# CVE-2026-27939: Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass

> Authenticated users can bypass verification steps to gain elevated privileges and access sensitive operations in Statamic CMS.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 27 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-rw9x-pxqx-q789

## What is CVE-2026-27939?

CVE-2026-27939 is a high-severity vulnerability in statamic cms, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Statmatic is a Laravel and Git powered content management system (CMS). Starting in version 6.0.0 and prior to version 6.4.0, Authenticated Control Panel users may under certain conditions obtain elevated privileges without completing the intended verification step. This can allow access to sensitive operations and, depending on the user’s existing permissions, may lead to privilege escalation. This has been fixed in 6.4.0.

Weakness: CWE-287 (Improper Authentication)

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

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.4.0 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.4.0 |

Products: Statamic Statamic.

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

Upgrade statamic/cms to 6.4.0 or later.

## Is CVE-2026-27939 being exploited?

There is no known exploitation of CVE-2026-27939 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-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)
- [CVE-2026-33172](https://insights.sbomify.com/CVE-2026-33172/): Statamic has Stored XSS via SVG Sanitization Bypass (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27939 is a high-severity vulnerability in statamic cms, published on 27 Feb 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-27939 in the wild and no public exploit code.

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

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

## Sources

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

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