Summary
Craft CMS Vulnerable to Stored XSS via User Group Name in User Permissions Page
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
- Log in to the control panel as an admin
- Navigate to Settings → Users → User Groups
- Create or edit a user group and set the Name field to:
<img src=x onerror="alert('XSS')" hidden> - Save the user group
- Navigate to Users and edit any user (
/admin/users/{id}) - Click on the Permissions tab
- XSS executes
Mitigation
Sanitize user group names when rendering in the user permissions template.
References
Impact
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-G3HP-VVQF-8VW6? GHSA-G3HP-VVQF-8VW6 is a low-severity cross-site scripting (XSS) vulnerability in craftcms/cms (composer), affecting versions >= 5.0.0-RC1, <= 5.8.21. It is fixed in 5.8.22. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of craftcms/cms are affected by GHSA-G3HP-VVQF-8VW6? craftcms/cms (composer) versions >= 5.0.0-RC1, <= 5.8.21 is affected.
- Is there a fix for GHSA-G3HP-VVQF-8VW6? Yes. GHSA-G3HP-VVQF-8VW6 is fixed in 5.8.22. Upgrade to this version or later.
- Is GHSA-G3HP-VVQF-8VW6 exploitable, and should I be worried? Whether GHSA-G3HP-VVQF-8VW6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-G3HP-VVQF-8VW6 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-G3HP-VVQF-8VW6? Upgrade
craftcms/cmsto 5.8.22 or later.