/

CVE-2026-44212

Severity:

CRITICAL RISK

(9.3)

XSS in PrestaShop Back-Office Customer Service View

CVE-2026-44212

Deferred

Vulnerability type

Category:

Cross-Site Scripting (XSS)

CWE:

CWE-79

Impact:

Session Hijacking and Administrative Account Compromise via Stored XSS

Severity:

CRITICAL RISK

(9.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

PrestaShop's back-office Customer Service view contains a stored Cross-Site Scripting (XSS) flaw where attacker-controlled data from the public "Contact Us" form is rendered without proper sanitization.

An unauthenticated attacker can submit a malicious email address that is stored in the database and later executed in a back-office employee's browser, enabling session hijacking and potentially full back-office takeover when the affected thread is viewed.

Affected context

This vulnerability arises in PrestaShop installations where:

  • The public "Contact Us" form is exposed to unauthenticated visitors.
  • Submitted customer messages are later viewed in the back-office Customer Service interface.
  • User-supplied fields (such as the email address) are rendered in the back-office UI without robust output encoding or sanitization.

The issue is triggered when a staff member opens a customer thread that includes data containing attacker-supplied script content.

Exploit preconditions

  • Attack surface: Public-facing "Contact Us" form on the storefront.
  • Required access: None; the attacker can be fully unauthenticated.
  • Trigger point: A back-office employee opens or previews the affected customer thread in the Customer Service view.
  • Why exploitation is possible: Untrusted data from the email field is stored and later injected into the back-office HTML context without context-appropriate output encoding, allowing arbitrary script execution in the employee's browser.

Why this happens

The core issue is improper neutralization of untrusted input before it is included in an HTML response, mapping directly to CWE-79: Improper Neutralization of Input During Web Page Generation (Cross-Site Scripting).

Data from the public "Contact Us" form—particularly the email address—gets persisted and then displayed in the back-office UI without consistent, context-aware output encoding (for example, HTML or attribute encoding).

This insecure pattern treats user-supplied values as safe content in a privileged administrative interface, which allows attackers to inject script code that executes in the staff member's browser with their authenticated session.

Potential impact

  • Hijacking of back-office employee sessions via theft of authentication cookies or tokens.
  • Full compromise of the PrestaShop back-office, including administrative actions under the victim's account.
  • Creation or modification of products, discounts, payment settings, or orders.
  • Exfiltration of customer data, including personally identifiable information and order histories.
  • Injection of further malicious content into storefront pages to attack end customers.
  • Use of compromised back-office access as a pivot point for broader infrastructure attacks.

General mitigation guidance

Effective mitigation focuses on treating all user-supplied input as untrusted and applying context-aware output encoding whenever it is rendered:

  • Ensure that every field originating from public forms, including email fields, is correctly escaped before being inserted into HTML, attributes, or JavaScript contexts.
  • Normalize and validate customer-facing input to reject or strictly constrain unexpected characters where feasible, while avoiding reliance on input filtering alone.
  • Enforce a consistent templating system that encodes variables by default, requiring explicit opt-out for rare safe cases.
  • Apply the principle of least privilege to back-office sessions and reduce their lifespan to limit the damage from potential session hijacking.
  • Consider enabling security headers such as Content Security Policy (CSP) to reduce the impact of XSS if it occurs, recognizing that CSP is a defense-in-depth measure, not a primary fix.

How teams detect issues like this

Detection typically combines code-level analysis and behavioral monitoring:

  • Use static analysis or linters to flag direct insertion of request data (e.g., form fields, POST/GET parameters) into templates without encoding functions.
  • During code review, look for HTML templates or view logic that echo raw database fields originating from public forms, especially in administrative interfaces.
  • Enforce secure coding guidelines that mandate output encoding helpers in rendering layers, and use automated checks in CI to prevent regressions.
  • Monitor application logs and browser-side telemetry for unusual script execution patterns in back-office pages, which may signal exploitation of stored XSS.

Sources

SourceLink
github.comgithub.com/PrestaShop/PrestaShop/security/advisories/GHSA-w9f3-qc75-qgx9

Frequently asked

questions

Yes. An attacker can exploit this vulnerability remotely by submitting a crafted message through the public "Contact Us" form; no prior authentication is required. Exploitation completes when a back-office employee views the stored thread.

No. The attacker only needs access to the public-facing contact form. The malicious payload is executed in the context of a logged-in back-office employee when they open the affected customer thread.

The safest approach is to ensure that all user-supplied data is properly escaped or encoded at the point of output, using a templating system or helper functions that apply context-appropriate encoding by default. Reviewing the back-office views to remove any raw rendering of untrusted fields is essential.

Adopt a defense-in-depth strategy: enforce secure coding standards that mandate output encoding, use frameworks that default to safe rendering, add automated static analysis to flag unsafe patterns, and complement this with strong CSP policies and regular security-focused code reviews of administrative interfaces.

Find out what's already
exploitable in your codebase.