Skip to content

PrestaShop XSS can be stored in DB from "add a message form" in order detail page (FO)

Moderate severity GitHub Reviewed Published Jan 2, 2024 in PrestaShop/PrestaShop • Updated Jan 3, 2024

Package

composer prestashop/prestashop (Composer)

Affected versions

< 8.1.3

Patched versions

8.1.3

Description

Impact

The isCleanHtml method is not used on this this form, which makes it possible to store an xss in DB.
The impact is low because the html is not interpreted in BO, thanks to twig's escape mechanism.
In FO, the xss is effective, but only impacts the customer sending it, or the customer session from which it was sent.

Be careful if you have a module fetching these messages from the DB and displaying it without escaping html.

Patches

8.1.x

Reporter

Reported by Rona Febriana (linkedin: https://www.linkedin.com/in/rona-febriana/)

References

@matthieu-rolland matthieu-rolland published to PrestaShop/PrestaShop Jan 2, 2024
Published by the National Vulnerability Database Jan 2, 2024
Published to the GitHub Advisory Database Jan 3, 2024
Reviewed Jan 3, 2024
Last updated Jan 3, 2024

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
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
Low

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:L/PR:L/UI:R/S:C/C:L/I:N/A:L

EPSS score

0.046%
(18th percentile)

Weaknesses

CVE ID

CVE-2024-21628

GHSA ID

GHSA-vr7m-r9vm-m4wf

Source code

Credits

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