Craft CMS Vulnerable to Stored XSS via User Group Name in User Permissions Page
Published 11 Mar 2026 · Updated 6 Aug 2026
Affected package
- Affected
- >=5.0.0-RC1 <5.8.22
- Fixed in
- 5.8.22
composer require craftcms/cms:^5.8.22Details
Summary
A stored XSS vulnerability exists in the User Permissions page. The User Group name is rendered without proper HTML escaping in the permissions section, allowing an attacker to execute arbitrary JavaScript when another user views or edits a user's permissions.
> [!NOTE] > This is a separate vulnerability from the previously reported "Stored XSS via User Group Name in User Settings Page" and "Multiple Stored XSS in User Group Edit Page". This affects a different sink: the individual user's permissions page.
Proof of Concept
Required Permissions
- Admin access
allowAdminChangesis enabled in production, which is against our security recommendations.
Steps to Reproduce
1. Log in to the control panel as an admin 2. Navigate to Settings → Users → User Groups 3. Create or edit a user group and set the Name field to:
<img src=x onerror="alert('XSS')" hidden>4. Save the user group
5. Navigate to Users and edit any user (/admin/users/{id})
6. Click on the Permissions tab
7. XSS executes
Mitigation
Sanitize user group names when rendering in the user permissions template.
References
https://github.com/craftcms/cms-ghsa-4mgv-366x-qxvx/pull/2
Is GHSA-g3hp-vvqf-8vw6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected craftcms/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.