# CVE-2026-71293: Statamic CMS Unguarded Exposure of 2FA Recovery Codes via Antlers current_user Variable

> Statamic CMS exposes raw two-factor recovery codes via the current_user variable, allowing attackers to bypass 2FA and take over accounts.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-jppw-r5j3-xf7x

## What is CVE-2026-71293?

CVE-2026-71293 is a medium-severity vulnerability in statamic cms, published on 5 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Statamic CMS's user-augmentation resolver, AugmentedUser::get in src/Auth/AugmentedUser.php, contains an explicit case for the handle that returns the user's raw two-factor recovery codes with no access restriction.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including statamic/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 to 6.30.0 | None |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 to 6.30.0 | None |

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

No fix has been published for CVE-2026-71293 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71293 is a medium-severity vulnerability in statamic cms, published on 5 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71293 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected from 6.0.0-alpha.1 up to 6.30.0; no fix listed
- statamic/cms (Packagist): affected from 6.0.0-alpha.1 up to 6.30.0; no fix listed

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

## Sources

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

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