CVE-2024-21627

PrestaShop some attribute not escaped in Validate::isCleanHTML method

Description

Some event attributes are not detected by the isCleanHTML method

Workarounds

The best workaround is to use the HTMLPurifier library to sanitize html input coming from users. The library is already available as a dependency in the PrestaShop project. Beware though that in legacy object models, fields of HTML type will call isCleanHTML.

Reporters

Reported by Antonio Russo (@Antonio-R1 on GitHub) and Antonio Rocco Spataro (@antoniospataro on GitHub).

Some modules using the isCleanHTML method could be vulnerable to xss

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-21627 has a CVSS score of 8.1 (High). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.1.3, 1.7.8.11); upgrading removes the vulnerable code path.

Kodem intelligence

8.1.3, 1.7.8.11

1. What is CVE-2024-21627? CVE-2024-21627 is a high-severity improper input validation vulnerability in prestashop/prestashop (composer), affecting versions >= 8.0.0-beta.1, < 8.1.3. It is fixed in 8.1.3, 1.7.8.11. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2024-21627? CVE-2024-21627 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of prestashop/prestashop are affected by CVE-2024-21627? prestashop/prestashop (composer) versions >= 8.0.0-beta.1, < 8.1.3 is affected.
4. Is there a fix for CVE-2024-21627? Yes. CVE-2024-21627 is fixed in 8.1.3, 1.7.8.11. Upgrade to this version or later.
5. Is CVE-2024-21627 exploitable, and should I be worried? Whether CVE-2024-21627 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-21627 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-21627?
   • Upgrade prestashop/prestashop to 8.1.3 or later
   • Upgrade prestashop/prestashop to 1.7.8.11 or later

Other vulnerabilities in prestashop/prestashop