dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-44212

CRITICAL · 9.3 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PrestaShop is an open source e-commerce web application. Prior to 8.2.6 and 9.1.1, there is a stored Cross-Site Scripting (XSS) vulnerability in the PrestaShop back-office Customer Service view. An unauthenticated attacker can submit the public Contact Us form with a malicious email address. The payload is stored in the database and executed when a back-office employee opens the affected customer thread, enabling session hijacking and full back-office takeover. This vulnerability is fixed in 8.2.6 and 9.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored XSS vulnerability exists in PrestaShop's public Contact Us form where an attacker can submit a malicious email address that gets stored in the database. When a back-office employee views the affected customer thread, the payload executes in their session, enabling session hijacking and full back-office account takeover.

MitigationUpgrade PrestaShop to version 8.2.6 or 9.1.1 or later to apply the security patch that properly sanitizes email input in the Contact Us form.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify PrestaShop installation
    Check your web server for PrestaShop files - look for the /classes or /modules directories containing PrestaShop core files, or check the database for tables with 'ps_' prefix that are typical of PrestaShop installations.
    Affected if PrestaShop software is present on the server
  2. Determine installed PrestaShop version
    Open the /app/AppKernel.php file and locate the version constant, or check the /config/autoload.php for the VERSION constant, or query your database for version information in the ps_configuration table.
    Affected if The installed version is prior to 8.2.6 or 9.1.1, or the version cannot be determined and you suspect an older release
  3. Verify Customer Service module is active
    Check if the Contact Us form functionality is enabled by examining the ps_contact_module table in the database, or log into the back-office and navigate to Customer Service > Customer Service to confirm the module is accessible.
    Affected if The Customer Service module is installed and accessible to employees
  4. Inspect customer thread records for suspicious data
    Query the ps_customer_thread table in your database, specifically examining the email field for unusual characters like <script>, javascript:, onerror=, or encoded payloads. Look for any records with email addresses containing HTML or JavaScript code.
    Affected if Any customer thread records contain email addresses with HTML tags or script content that did not originate from your organization
  5. Review recent contact form submissions
    Check the ps_contact_form data or equivalent contact submission logs for any submissions from unauthenticated sources with abnormally formatted email addresses, particularly those submitted within the past months.
    Affected if There are contact form submissions with unexpected email address patterns that could indicate exploitation attempts

You are affected if PrestaShop is installed with a version prior to 8.2.6 or 9.1.1 and the Customer Service module is active, particularly if customer thread records contain unexpected HTML or script content in email fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade PrestaShop to version 8.2.6 or 9.1.1 or later to apply the security patch that properly sanitizes email input in the Contact Us form.

Recommended fix High confidence

PrestaShop 8.2.6 (for 8.x users) or PrestaShop 9.1.1 (for 9.x users)

  1. 1. Backup your PrestaShop database and files before any upgrade
  2. 2. Identify your current PrestaShop version (8.x or 9.x branch)
  3. 3. If on PrestaShop 8.x: Upgrade to version 8.2.6 or later
  4. 4. If on PrestaShop 9.x: Upgrade to version 9.1.1 or later
  5. 5. Verify the upgrade by checking the PrestaShop admin footer shows the new version
  6. 6. Test the Contact Us form submission to confirm it properly sanitizes email input
  7. 7. Clear any cached data in var/cache and var/app/cache directories
  8. 8. Review customer service threads for any existing malicious payloads submitted prior to the patch
Caveat Review PrestaShop migration notes between your current version and target version for potential module/compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data