CVE-2024-34716

PrestaShop cross-site scripting via customer contact form in FO, through file upload

Workarounds

As long as you have not upgraded to 8.1.6, a simple workaround is to disable the customer-thread feature-flag.

Thank you to Ayoub AIT ELMOKHTAR, who discovered this vulnerability and share it with the PrestaShop team.

Only PrestaShops with customer-thread feature flag enabled are impacted, starting from PrestaShop 8.1.0.

The impact is substantial, when the customer thread feature flag is enabled, through the front-office contact form, a hacker can upload a malicious file containing an XSS that will be executed when an admin opens the attached file in back office.

Consequence: the script injected can access the session and the security token, which allows it to perform any authenticated action in the scope of the administrator's right.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-34716 has a CVSS score of 9.6 (Critical). The vector is network-reachable, no 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.6); upgrading removes the vulnerable code path.

Kodem intelligence

This vulnerability is patched in 8.1.6.

1. What is CVE-2024-34716? CVE-2024-34716 is a critical-severity cross-site scripting (XSS) vulnerability in prestashop/prestashop (composer), affecting versions >= 8.1.0, < 8.1.6. It is fixed in 8.1.6. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-34716? CVE-2024-34716 has a CVSS score of 9.6 (Critical). 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-34716? prestashop/prestashop (composer) versions >= 8.1.0, < 8.1.6 is affected.
4. Is there a fix for CVE-2024-34716? Yes. CVE-2024-34716 is fixed in 8.1.6. Upgrade to this version or later.
5. Is CVE-2024-34716 exploitable, and should I be worried? Whether CVE-2024-34716 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-34716 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-34716? Upgrade prestashop/prestashop to 8.1.6 or later.

Other vulnerabilities in prestashop/prestashop