Summary
Craft Commerce has stored XSS in Inventory Location Name
A stored XSS vulnerability exists in the Commerce Settings - Inventory Locations page. The Name field is rendered without proper HTML escaping, allowing an attacker to execute arbitrary JavaScript.
This XSS triggers when an administrator (or user with product editing permissions) creates or edits a variant product.
Proof of Concept
Permissions Required
General
- Access the control panel
- Access Craft Commerce
Craft Commerce
- Manage inventory locations
Steps to Reproduce
- Log in to the control panel
- Navigate to Commerce → Inventory Locations
- Create or edit a location
- Set Name to the following payload:
<img src=x onerror="alert('XSS')"> - Save the location
- Navigate to Commerce → Products and click "New Product" and click "New product variant"
- The Inventory Location table loads, rendering the Inventory Location Name
- XSS executes
Mitigation
Sanitize the inventory location name field when rendering in the "Track Inventory" table.
Impact
- Potential Session Hijacking
- Potential Database Exfiltration
- Potential Account Takeover by forcing a password change on the victim’s account.
- Potential Privilege escalation, or creating new admin users.
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-29176? CVE-2026-29176 is a medium-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-29176? craftcms/commerce (composer) versions >= 5.0.0, <= 5.5.2 is affected.
- Is there a fix for CVE-2026-29176? Yes. CVE-2026-29176 is fixed in 5.5.3. Upgrade to this version or later.
- Is CVE-2026-29176 exploitable, and should I be worried? Whether CVE-2026-29176 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-29176 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-29176? Upgrade
craftcms/commerceto 5.5.3 or later.