# Statamic CMS exposes two-factor recovery codes through dynamic Antlers rendering

Advisory record · `GHSA-jppw-r5j3-xf7x`

- **Identifiers:** `GHSA-jppw-r5j3-xf7x` · `CVE-2026-71293` · `PKSA-rsd9-mj5m-pj4f`
- **State:** Confirmed
- **Severity:** CVSS 6.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 5 Aug 2026
- **Updated:** 1 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Aug 2026, 15:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `statamic/cms` (Packagist): affected `>=6.0.0-alpha.1, <=6.30.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Statamic CMS (Packagist statamic/cms, versions 6.0.0-alpha.1 through 6.30.0) can render users' two-factor recovery codes into page HTML when dynamic Antlers rendering is enabled on a field. An attacker needs that option enabled through blueprint configuration, plus the ability to view or capture the rendered page, such as a shared page or a link that makes a victim render it, and could then use the codes to bypass two-factor authentication. No fixed version is listed.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.2 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N`, from CNA (TuranSec)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 31st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:06 UTC: First seen by agentprime
- 31 Oct 2026, 14:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jppw-r5j3-xf7x)

## Sources

- [GitHub Advisory Database: GHSA-jppw-r5j3-xf7x](https://github.com/advisories/GHSA-jppw-r5j3-xf7x)
- [OSV: GHSA-jppw-r5j3-xf7x](https://osv.dev/vulnerability/GHSA-jppw-r5j3-xf7x)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-71293>
- <https://github.com/statamic/cms>
- <https://github.com/statamic/cms/blob/master/src/Auth/AugmentedUser.php>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jppw-r5j3-xf7x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jppw-r5j3-xf7x/>. Everything for agents: <https://agentprime.io/llms.txt>.