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
- Log in as attacker with admin permissions.
- Go to Commerce -> Settings -> Product Types (
/admin/commerce/settings/producttypes).
- Create a new Product Type.
- Set Name to:
<img src=x onerror="alert('XSS-ProductType')" hidden>
- Save the Product Type.
- Go to Users -> Edit any user -> Click on Permissions tab (
/admin/users/{UserID}/permissions).
- Alert fires instantly (when the Product Type checkbox renders).
References
7e1dedf
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)
Steps to Reproduce
/admin/commerce/settings/producttypes)./admin/users/{UserID}/permissions).References
7e1dedf