How severe is GHSA-6j87-m5qx-9fqp?

No CVSS score has been assigned to GHSA-6j87-m5qx-9fqp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6j87-m5qx-9fqp?

GHSA-6j87-m5qx-9fqp affects the following packages: craftcms/cms (Packagist), craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6j87-m5qx-9fqp?

Update craftcms/cms to 4.16.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6j87-m5qx-9fqp is resolved across your whole dependency graph.

How do I detect GHSA-6j87-m5qx-9fqp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6j87-m5qx-9fqp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6j87-m5qx-9fqp?

O3 pinpoints whether GHSA-6j87-m5qx-9fqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6j87-m5qx-9fqp actively exploited in the wild?

No public exploit code has been indexed for GHSA-6j87-m5qx-9fqp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6j87-m5qx-9fqp published, and has it been updated?

GHSA-6j87-m5qx-9fqp was published on February 25, 2026 and was last updated on February 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-6j87-m5qx-9fqp

Craft CMS has Stored XSS in Table Field in its "Row Heading" Column Type

Published

Feb 25, 2026

Updated

Feb 25, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘craftcms/cms🐘craftcms/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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
allowAdminChanges must 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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 4.5.0-beta.1&&< 4.16.19	4.16.19
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.8.23	5.8.23

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update craftcms/cms to 4.16.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6j87-m5qx-9fqp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6j87-m5qx-9fqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6j87-m5qx-9fqp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 * `allowAdminChanges` must be enabled in production, which is [against security recommendations](https://craftcms.com/knowledge-base/securing-craft#set-allowAdminChanges-to-false-in-production). ## Steps to Reproduce 1. Navigate to **Settin

O3 Security · Impact-Aware SCA

Is GHSA-6j87-m5qx-9fqp in your dependencies?

O3 detects GHSA-6j87-m5qx-9fqp across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works