How severe is GHSA-3jh3-prx3-w6wc?

No CVSS score has been assigned to GHSA-3jh3-prx3-w6wc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3jh3-prx3-w6wc?

GHSA-3jh3-prx3-w6wc affects the following packages: craftcms/cms (Packagist), craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3jh3-prx3-w6wc?

Update craftcms/cms to 4.16.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jh3-prx3-w6wc is resolved across your whole dependency graph.

How do I detect GHSA-3jh3-prx3-w6wc 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-3jh3-prx3-w6wc 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-3jh3-prx3-w6wc?

O3 pinpoints whether GHSA-3jh3-prx3-w6wc 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-3jh3-prx3-w6wc actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jh3-prx3-w6wc 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.

What is the EPSS score for GHSA-3jh3-prx3-w6wc?

GHSA-3jh3-prx3-w6wc has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3jh3-prx3-w6wc?

GHSA-3jh3-prx3-w6wc is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3jh3-prx3-w6wc published, and has it been updated?

GHSA-3jh3-prx3-w6wc was published on February 23, 2026 and was last updated on February 24, 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-3jh3-prx3-w6wc

Craft CMS has Stored XSS in Table Field via "HTML" Column Type

Also known asCVE-2026-27126

Published

Feb 23, 2026

Updated

Feb 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk12th percentile+0.21%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 html column type. The application fails to sanitize the input, 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 our 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 Single-line text
- Note: The vulnerable Column Type is html, but it's not available in the UI dropdown.
In Default Values section, add a row with the following payload:
```
<img src=x onerror="alert('XSS')">
```
Enable Static Rows
Intercept the Save Field request using a proxy tool (e.g., Burp Suite) or use cURL directly
Modify the request body and change the types[craft-fields-Table][columns][col3][type] parameter from singleline to html
Forward the request to save the field
Use the field in any object (e.g. user profile fields) → then visit the any user's profile
Notice the XSS execution
The XSS will also trigger when an administrator attempts to edit this field, as the malicious payload is executed within the field configuration page, too.

Resources

https://github.com/craftcms/cms/commit/f5d488d9bb6eff7670ed2c2fe30e15692e92c52b

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 4.5.0-RC1&&< 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-3jh3-prx3-w6wc 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-3jh3-prx3-w6wc 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-3jh3-prx3-w6wc. 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 `html` column type. The application fails to sanitize the input, 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 our security recommendations](https://craftcms.com/knowledge-base/securing-craft#set-allowAdminChanges-to-false-in-production). ## Steps to Reproduce 1. Navigate to **Settings** → **Fields** a

O3 Security · Impact-Aware SCA

Is GHSA-3jh3-prx3-w6wc in your dependencies?

O3 detects GHSA-3jh3-prx3-w6wc 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