Quick answers
- Is CVE-2026-44212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44212 being exploited in the wild.
- How severe is CVE-2026-44212?
- Critical severity, with a CVSS score of 9.3, published 14 May 2026.
- Which products and versions are affected?
- prestashop/prestashop (Packagist) ECOSYSTEM:introduced=0,fixed=8.2.6; PrestaShop < 8.2.6, < 9.1.1.
- Is there a fix for CVE-2026-44212?
- Yes. prestashop/prestashop (Packagist): upgrade to 8.2.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44212 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-44212?
- Check whether you run prestashop/prestashop (Packagist) or PrestaShop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- prestashop/prestashop (Packagist): upgrade to 8.2.6 or later
composer require prestashop/prestashop:^8.2.6
Technical details
A stored Cross-Site Scripting (XSS) vulnerability exists in the PrestaShop back-office Customer Service view due to improper neutralization of input in the email address field. An unauthenticated attacker can submit a malicious payload through the public-facing 'Contact Us' form. This payload is stored in the database and subsequently executed in the browser of a back-office employee when they open the affected customer service thread. Because the vulnerability results in a scope change (S:C), it allows for session hijacking and full administrative takeover of the PrestaShop instance. The issue is resolved in versions 8.2.6 and 9.1.1.
Affected products
- PrestaShop PrestaShop < 8.2.6, < 9.1.1
Identifiers
- CVE-2026-44212
- GHSA-w9f3-qc75-qgx9
Timeline
- 2026-05-04: advisory: Original GitHub security advisory published
- 2026-05-14: disclosed: CVE published to NVD