Skip to content

ps_contactinfo has a potential XSS due to usage of the nofilter tag in template

Moderate severity GitHub Reviewed Published Jan 22, 2025 in PrestaShop/ps_contactinfo • Updated Jan 22, 2025

Package

composer prestashop/ps_contactinfo (Composer)

Affected versions

<= 3.3.2

Patched versions

3.3.3

Description

Impact

This can not be exploited in a fresh install of PrestaShop, only shops made vulnerable by third party modules are concerned.

For example, if your shop has a third party module vulnerable to SQL injections, then ps_contactinfo might execute a stored XSS in FO.

Patches

The long term fix is to have all your modules maintained and updated.
The fix on ps_contactinfo will keep formatted addresses from displaying an xss stored in the database.

Workarounds

none

References

none

References

@matthieu-rolland matthieu-rolland published to PrestaShop/ps_contactinfo Jan 22, 2025
Published by the National Vulnerability Database Jan 22, 2025
Published to the GitHub Advisory Database Jan 22, 2025
Reviewed Jan 22, 2025
Last updated Jan 22, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:H

EPSS score

Weaknesses

CVE ID

CVE-2025-24027

GHSA ID

GHSA-35pq-7pv2-2rfw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.