CVE-2026-25482: Craft Commerce has Stored DOM XSS in Order Status Name (Reflects in "Recent Orders" Dashboard Widget)
Summary A stored DOM XSS vulnerability exists in the "Recent Orders" dashboard widget. The Order Status Name is rendered via JavaScript string concatenation without proper escaping, allowing script execution when any admin visits the dashboard. Users are recommended to update to the patched 5.5.2 release to mitigate the issue.
Published Feb 2, 2026 · Updated Feb 3, 2026
Affected packages
craftcms/commerce
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.0.0, <= 5.5.1
- Fixed in
- 5.5.2
- Check
composer show craftcms/commerce
craftcms/commerce
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.0.0-RC1, <= 4.10.0
- Fixed in
- 4.10.1
- Check
composer show craftcms/commerce
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A stored DOM XSS vulnerability exists in the "Recent Orders" dashboard widget. The Order Status Name is rendered via JavaScript string concatenation without proper escaping, allowing script execution when any admin visits the dashboard.
Users are recommended to update to the patched 5.5.2 release to mitigate the issue.
---
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 new order status (e.g., "Pending")
- Set the Name field to:
- Save the order status
- Go to Commerce Orders & make some orders with different statuses (e.g. "New" & "the malicious created status")
- Go to the Dashboard (
/admin/dashboard) & Add "Recent Orders" widget and pick the same 2 statuses for orders - Notice the XSS execution
---
Technical Details
File: vendor/craftcms/commerce/src/templates/_components/widgets/orders/recent/body.twig
Root Cause: value.name (the Order Status Name) is concatenated directly into the HTML string without sanitization. When JavaScript inserts this HTML into the DOM, any malicious tags/scripts in the name are executed.
---
Mitigation
Use Craft.escapeHtml() in the callback:
callback: function(value) {
return '' + Craft.escapeHtml(value.name) + '';
}Resources:
https://github.com/craftcms/commerce/commit/d94d1c9832a47a1c383e375ae87c46c13935ba65
Credited to mHe4am.
References
- https://github.com/craftcms/commerce/security/advisories/GHSA-frj9-9rwc-pw9j
- https://github.com/craftcms/commerce/commit/d94d1c9832a47a1c383e375ae87c46c13935ba65
- https://github.com/craftcms/commerce/releases/tag/4.10.1
- https://github.com/craftcms/commerce/releases/tag/5.5.2
- https://nvd.nist.gov/vuln/detail/CVE-2026-25482
- https://github.com/advisories/GHSA-frj9-9rwc-pw9j
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-55795
Craft Commerce: Coupon Code Brute-Force via Rate Limit Bypass
medium6.9Jun 19, 2026GHSA-78vr-q6cf-c7p6
Craft Commerce: Partial Payment Amount Without Lower Bound Validation
medium6.9Jun 19, 2026CVE-2026-32270
Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments
low1.7Apr 14, 2026CVE-2026-32271
Craft Commerce has a SQL Injection can lead to Remote Code Execution via TotalRevenue Widget
high8.7Apr 14, 2026CVE-2026-32272
Craft Commerce hasVariant/hasProduct Blind SQL Injection
high8.7Apr 14, 2026CVE-2026-29172
Craft Commerce is Vulnerable to SQL Injection in Commerce Purchasables Table Sorting
high8.7Mar 10, 2026
