GHSA-2h2m-v2mg-656c

Craft Commerce has Stored XSS in Product Type Name

Source: GitHub Advisory Database (reviewed) Moderate CVE-2026-25484

Packages

Ecosystem	Package	Affected	Fixed in
Packagist	craftcms/commerce	>= 5.0.0, < 5.5.2	5.5.2
Packagist	craftcms/commerce	>= 4.0.0-RC1, < 4.10.1	4.10.1

Details

As written in the advisory (Markdown source, shown as plain text).

## Summary Stored XSS via Product Type names. The name is not sanitized when displayed in user permissions settings. The vulnerable input (source) is in Commerce (Product Type settings), but the sink is in CMS user permissions settings. Reporting to Commerce GHSA since the input originates here. Users are recommended to update to the patched 5.5.2 release to mitigate the issue. --- ## Proof of Concept ### Required Permissions (Attacker) - Admin access (to edit Commerce settings) ### Steps to Reproduce 1. Log in as attacker with admin permissions. 2. Go to **Commerce** -> **Settings** -> **Product Types** (`/admin/commerce/settings/producttypes`). 3. Create a new Product Type. 4. Set **Name** to: ```html <img src=x onerror="alert('XSS-ProductType')" hidden> ``` 5. Save the Product Type. 6. Go to **Users** -> Edit any user -> Click on **Permissions** tab (`/admin/users/{UserID}/permissions`). 7. Alert fires instantly (when the Product Type checkbox renders). ## Resources https://github.com/craftcms/commerce/commit/7e1dedf06038c8e70dce0187b7048d4ab8ffb75c

References

External links from the advisory. They lead to third-party sites.