# CVE-2026-27593: Statamic is vulnerable to account takeover via password reset link injection

> Attackers can hijack user accounts by injecting password reset links, requiring the victim to click an unsolicited email link.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-jxq9-79vj-rgvw

## What is CVE-2026-27593?

CVE-2026-27593 is a critical authentication bypass vulnerability in statamic cms, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 6.3.3 and 5.73.10, an attacker may leverage a vulnerability in the password reset feature to capture a user's token and reset the password on their behalf. The attacker must know the email address of a valid account on the site, and the actual user must blindly click the link in their email even though they didn't request the reset. This has been fixed in 6.3.3 and 5.73.10.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 5.73.10 |
| `statamic/cms` | Packagist | All versions | 5.73.10 |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 | 6.7.1 |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 | 6.7.1 |

Products: Statamic Statamic.

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

Upgrade statamic/cms to a fixed version for your release line: 5.73.10 or 6.7.1.

## Is CVE-2026-27593 being exploited?

There is no known exploitation of CVE-2026-27593 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-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)
- [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-27593 and fix it if it is affected.

What it is: CVE-2026-27593 is a critical authentication bypass vulnerability in statamic cms, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27593 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 5.73.10
- statamic/cms (Packagist): affected all versions; fixed in 5.73.10
- statamic/cms (Packagist): affected from 6.0.0-alpha.1; fixed in 6.7.1
- statamic/cms (Packagist): affected from 6.0.0-alpha.1; fixed in 6.7.1

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

## Sources

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

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