# CVE-2026-32612: Statamic: privilege escalation via stored cross-site scripting

> Authenticated users can inject malicious scripts via color preferences, leading to privilege escalation when higher-privileged users impersonate them.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-hcch-w73c-jp4m

## What is CVE-2026-32612?

CVE-2026-32612 is a medium-severity cross-site scripting vulnerability in statamic cms, published on 12 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Statamic is a Laravel and Git powered content management system (CMS). Prior to 6.6.2, stored XSS in the control panel color mode preference allows authenticated users with control panel access to inject malicious JavaScript that executes when a higher-privileged user impersonates their account. This has been fixed in 6.6.2.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | From 6.0.0 | 6.6.2 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.6.2 |

Products: Statamic Statamic.

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

Upgrade statamic/cms to 6.6.2 or later.

## Is CVE-2026-32612 being exploited?

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

## Other vulnerabilities in statamic cms

- [CVE-2021-45364](https://insights.sbomify.com/CVE-2021-45364/): Code injection in n/a (critical 9.8)
- [CVE-2026-27593](https://insights.sbomify.com/CVE-2026-27593/): Statamic is vulnerable to account takeover via password reset link injection (critical 9.3)
- [CVE-2026-27939](https://insights.sbomify.com/CVE-2026-27939/): Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass (high 8.8)
- [CVE-2023-48217](https://insights.sbomify.com/CVE-2023-48217/): Remote code execution via form uploads in statamic/cms (high 8.8)
- [CVE-2017-11422](https://insights.sbomify.com/CVE-2017-11422/): Statamic framework Incorrect Permission Assignment (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32612 is a medium-severity cross-site scripting vulnerability in statamic cms, published on 12 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32612 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.6.2
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.6.2

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-32612/ (Markdown: https://insights.sbomify.com/CVE-2026-32612/index.md)
```

## Sources

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

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