craftcms/commerce
Affected
- introduced
5.0.0-RC1, fixed5.5.2(ecosystem)
Fixed versions
5.5.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-25486
Craft Commerce has Stored XSS in Shipping Methods Name Field Leading to Potential Privilege Escalation
Summary
A stored XSS vulnerability in Craft Commerce allows attackers to execute malicious JavaScript in an administrator’s browser. This occurs because the Shipping Methods Name field in the Store Management section is not properly sanitized before being displayed in the admin panel.
---
Proof of Concept
Requirments
Steps to Reproduce
/admin/commerce/store-management/primary/shippingmethods).<img src=x onerror="alert(document.domain)">
Privilege Escalation to Administrator:
<UserID> with your attacker id:<img src=x onerror="fetch('/admin/users/<UserID>/permissions',{method:'POST',body:`CRAFT_CSRF_TOKEN=${Craft.csrfTokenValue}&userId=<UserID>&admin=1&action=users/save-permissions`,headers:{'content-type':'application/x-www-form-urlencoded'}})">
The privilege escalation requires an elevated session. In a real-world scenario, an attacker can automate the process by forcing a logout if the victim’s session is stale; upon re-authentication, the stored XSS payload executes within a fresh, elevated session to complete the attack.
Or even easier (and smarter), an attacker (using the XSS) can create a fake 'Session Expired' login modal overlay. Since it’s on the trusted domain, administrators will likely enter their credentials, sending them directly to the attacker.
Resources:
https://github.com/craftcms/commerce/commit/fa273330807807d05b564d37c88654cd772839ee
Medium Basis: The source's own band: MODERATE
5.0.0-RC1, fixed 5.5.2 (ecosystem)5.5.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0