How severe is GHSA-3x4w-mxpf-fhqq?

No CVSS score has been assigned to GHSA-3x4w-mxpf-fhqq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3x4w-mxpf-fhqq?

GHSA-3x4w-mxpf-fhqq affects the following packages: craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3x4w-mxpf-fhqq?

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

How do I detect GHSA-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq?

O3 pinpoints whether GHSA-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq actively exploited in the wild?

No public exploit code has been indexed for GHSA-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq?

GHSA-3x4w-mxpf-fhqq has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th 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-3x4w-mxpf-fhqq?

GHSA-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq published, and has it been updated?

GHSA-3x4w-mxpf-fhqq was published on March 18, 2026 and was last updated on March 20, 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-3x4w-mxpf-fhqq

Craft CMS Vulnerable to Stored XSS in Revision Context Menu

Also known asCVE-2026-33051

Published

Mar 18, 2026

Updated

Mar 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk15th percentile+0.22%

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

1 pkg affected

🐘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

The revision/draft context menu in the element editor renders the creator’s fullName as raw HTML due to the use of Template::raw() combined with Craft::t() string interpolation. A low-privileged control panel user (e.g., Author) can set their fullName to an XSS payload via the profile editor, then create an entry with two saves.

If an administrator is logged in and executes a specifically crafted payload while an elevated session is active, the attacker’s account can be elevated to administrator.

Users should update to Craft 5.9.11 with the patch to mitigate the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.9.0-beta.1&&< 5.9.11	5.9.11

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 5.9.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq 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-3x4w-mxpf-fhqq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The revision/draft context menu in the element editor renders the creator’s `fullName` as raw HTML due to the use of `Template::raw()` combined with `Craft::t()` string interpolation. A low-privileged control panel user (e.g., Author) can set their fullName to an XSS payload via the profile editor, then create an entry with two saves. If an administrator is logged in and executes a specifically crafted payload while an elevated session is active, the attacker’s account can be elevated to administrator. Users should update to Craft 5.9.11 with the patch to mitigate the issue.

O3 Security · Impact-Aware SCA

Is GHSA-3x4w-mxpf-fhqq in your dependencies?

O3 detects GHSA-3x4w-mxpf-fhqq 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