How severe is CVE-2026-29173?

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

Which packages are affected by CVE-2026-29173?

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

How do I fix CVE-2026-29173?

Update craftcms/commerce to 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-29173 is resolved across your whole dependency graph.

How do I detect CVE-2026-29173 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-29173 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-29173 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-29173 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-29173?

CVE-2026-29173 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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-29173?

CVE-2026-29173 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-29173 published, and has it been updated?

CVE-2026-29173 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-29173 — commerce

Fix: craftcms/commerce@60cdc50

CVE-2026-29173 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 while updating Order Status from Orders Table

Also known asGHSA-mqxf-2998-c6cp

Published

Mar 10, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 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-29173.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐘craftcms/commerce🐘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 when a user tries to update the Order Status from the Commerce Orders Table. The Order Status Name is rendered without proper escaping, allowing script execution to occur.

Proof of Concept

Required Permissions

Admin access (to edit/create Order Statuses)

Steps to Reproduce

Log in with an admin account
Navigate to Commerce → Settings → Order Statuses
Create a new order status
Set the Name field to:

<img src=x onerror="alert('Order Statuses XSS')">

Save the order status
Go to Commerce → Orders (make sure you placed any orders)
From the left panel, select any Order Status (e.g., New)
Select any order from the orders table → Click on the Gear Icon → then click "Update Order Status..."
Notice the XSS execution

Affected Packages

2 total 2 fixed

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

Affected Products

1 product · 2 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 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-29173 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 when a user tries to update the Order Status from the Commerce Orders Table. The Order Status Name is rendered without proper escaping, allowing script execution to occur. --- ## Proof of Concept ### Required Permissions - Admin access (to edit/create Order Statuses) ### Steps to Reproduce 1. Log in with an admin account 2. Navigate to **Commerce** → **Settings** → **Order Statuses** 3. Create a new order status 4. Set the **Name** field to: ```html <img src=x onerror="alert('Order Statuses XSS')"> ``` 5. Save the order status 6. Go to Commerce →

O3 Security · Impact-Aware SCA

Is CVE-2026-29173 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works