# CVE-2026-33051: Craft CMS Vulnerable to Stored XSS in Revision Context Menu

> Low-privileged users can inject scripts via profile names to escalate privileges to administrator in Craft CMS.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-3x4w-mxpf-fhqq

## What is CVE-2026-33051?

CVE-2026-33051 is a medium-severity cross-site scripting vulnerability in Craftcms Craft Cms, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Craft CMS is a content management system (CMS). In versions 5.9.0-beta.1 through 5.9.10, 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. This issue has been fixed in version 5.9.11.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-33051?

2 open source packages ship an affected version, including craftcms/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | From 5.9.0-beta.1 | 5.9.11 |
| `craftcms/cms` | Packagist | From 5.9.0-beta.1 | 5.9.11 |

Products: Craftcms Craft Cms.

## How do I fix CVE-2026-33051?

Upgrade craftcms/cms to 5.9.11 or later.

## Is CVE-2026-33051 being exploited?

There is no known exploitation of CVE-2026-33051 in the wild and no public exploit code.

## Other vulnerabilities in Craftcms Craft Cms

- [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild)
- [CVE-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, exploited in the wild)
- [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild)
- [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild)
- [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33051 and fix it if it is affected.

What it is: CVE-2026-33051 is a medium-severity cross-site scripting vulnerability in Craftcms Craft Cms, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33051 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 5.9.0-beta.1; fixed in 5.9.11
- craftcms/cms (Packagist): affected from 5.9.0-beta.1; fixed in 5.9.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33051/ (Markdown: https://insights.sbomify.com/CVE-2026-33051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33051
- OSV: https://osv.dev/vulnerability/CVE-2026-33051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33051/
Summaries are generated and may contain mistakes; the official description above is the record.