How severe is CVE-2026-29176?

No CVSS score has been assigned to CVE-2026-29176 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-29176?

CVE-2026-29176 affects the following packages: craftcms/commerce (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-29176?

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-29176 is resolved across your whole dependency graph.

How do I detect CVE-2026-29176 in my Packagist dependencies?

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.

How do I mitigate CVE-2026-29176 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-29176 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-29176 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-29176?

CVE-2026-29176 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-29176?

CVE-2026-29176 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-29176 published, and has it been updated?

CVE-2026-29176 was published on March 10, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-29176 — commerce

Fix: craftcms/commerce@da143df

CVE-2026-29176 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.

Craft Commerce has Stored XSS in Inventory Location Name

Also known asGHSA-wj89-2385-gpx3

Published

Mar 10, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-29176.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘craftcms/commerce

Real-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

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

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.

Mitigation

Sanitize the inventory location name field when rendering in the "Track Inventory" table.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/commerce`	≥ 5.0.0&&< 5.5.3	5.5.3`composer require craftcms/commerce:^5.5.3`

Affected Products

1 product · 1 configurations

Application

craft commercecraftcms

≥ 5.0.0 && < 5.5.3

range

Detection & mitigation playbook

Open-source dependency

Detect
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-29176 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

## Summary 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 1. Log in to the control panel 2. Navigate to **Commerce → Inventory Locati

O3 Security · Impact-Aware SCA

Is CVE-2026-29176 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works