Summary
Craft CMS has Stored XSS in Table Field in its "Row Heading" Column Type
A stored Cross-site Scripting (XSS) vulnerability exists in the editableTable.twig component when using the Row Heading column type. The application fails to sanitize input within row headings, allowing an attacker to execute arbitrary JavaScript when another user views a page with the malicious table field.
Prerequisites
- An administrator account
allowAdminChangesmust be enabled in production, which is against security recommendations.
Steps to Reproduce
- Navigate to Settings → Fields and create a new field with Type: Table
- Add a Column Heading and set Column Type to
Row Heading - In Default Values section, add a row with the following payload:
<img src=x onerror="alert('XSS')"> - Enable
Static Rows - Use the field in any object (e.g., user profile fields) → then visit any user’s profile
- Notice the XSS execution
Resources
https://github.com/craftcms/cms/commit/7b372de262b8d9d2ce859f32780c3715719b6f5a
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
craftcms/cms to 4.16.19 or later; craftcms/cms to 5.8.23 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-6J87-M5QX-9FQP? GHSA-6J87-M5QX-9FQP is a low-severity cross-site scripting (XSS) vulnerability in craftcms/cms (composer), affecting versions >= 4.5.0-beta.1, <= 4.16.18. It is fixed in 4.16.19, 5.8.23. 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-6J87-M5QX-9FQP? craftcms/cms (composer) versions >= 4.5.0-beta.1, <= 4.16.18 is affected.
- Is there a fix for GHSA-6J87-M5QX-9FQP? Yes. GHSA-6J87-M5QX-9FQP is fixed in 4.16.19, 5.8.23. Upgrade to this version or later.
- Is GHSA-6J87-M5QX-9FQP exploitable, and should I be worried? Whether GHSA-6J87-M5QX-9FQP 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-6J87-M5QX-9FQP 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-6J87-M5QX-9FQP?
- Upgrade
craftcms/cmsto 4.16.19 or later - Upgrade
craftcms/cmsto 5.8.23 or later
- Upgrade