Skip to content

Possible XSS injection through Validate::isCleanHTML method

High severity GitHub Reviewed Published Apr 25, 2023 in PrestaShop/PrestaShop • Updated Nov 10, 2023

Package

composer prestashop/prestashop (Composer)

Affected versions

>= 8.0.0, < 8.0.4
< 1.7.8.9

Patched versions

8.0.4
1.7.8.9

Description

Impact

ValidateCore::isCleanHTML() method of Prestashop misses hijickable events which can lead to XSS injection, allowed by the presence of pre-setup @Keyframes methods.

This XSS which hijacks HTML attributes will be triggered without any interaction of the visitor/administrator which makes it as dangerous as a trivial XSS.

Contrary to most XSS which target HTML attributes and which are triggered without user interaction (such as onload / onerror which suffer from a very limited scope), this one can hijack every HTML element, which increases the danger due to a complete HTML elements scope.

Patches

The patch will be on PS 8.0.4 and PS 1.7.8.9

References

References

@mflasquin mflasquin published to PrestaShop/PrestaShop Apr 25, 2023
Published by the National Vulnerability Database Apr 25, 2023
Published to the GitHub Advisory Database Apr 25, 2023
Reviewed Apr 25, 2023
Last updated Nov 10, 2023

Severity

High

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
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:L/UI:R/S:C/C:H/I:H/A:H

EPSS score

0.204%
(58th percentile)

Weaknesses

CVE ID

CVE-2023-30838

GHSA ID

GHSA-fh7r-996q-gvcp

Source code

Credits

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