Craft Commerce has Stored XSS in Tax Zones (Name & Description) 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 Name & Description fields in Tax Zones are not properly sanitized before being displayed in the admin panel.

Proof of Concept

Requirments

• General permissions:
  • Access the control panel
  • Access Craft Commerce
• Craft Commerce permissions:
  • Manage store settings
  • Manage taxes
• An active administrator elevated session

Steps to Reproduce

1. Log in to the Admin Panel with the attacker account with the permissions mentioned above.
2. Navigate to Commerce -> Store Management -> Tax Zones (/admin/commerce/store-management/primary/taxzones).
3. Create a new tax zone.
4. In the Name or Description field, enter the following payload:

<img src=x onerror="alert(document.domain)">

4. Click Save and you’ll be redirected back to the previous page.
5. Notice the alert proving JavaScript execution. <img width="1904" height="418" alt="poc" src="https://github.com/user-attachments/assets/09bd993b-550e-40fe-b2d7-1608e25fbc01" />

Privilege Escalation to Administrator:

1. Do the same steps above, but replace the payload with a malicious one.
2. The following payload elevates the attacker’s account to Admin if there’s already an elevated session, replace the <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'}})">

4. In another browser, log in as an admin & go to the vulnerable page (tax zones page).
5. Go back to your attacker account & notice you are now an admin.

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.