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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-71293: 0.37% estimated exploitation activity in the next 30 days; percentile 31.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Statamic CMS's user-augmentation resolver, AugmentedUser::get() in src/Auth/AugmentedUser.php, contains an explicit case for the twofactorrecoverycodes handle that returns the user's raw two-factor recovery codes with no access restriction: if ($handle === 'twofactorrecoverycodes') { return new Value($this-data-get('twofactorrecoverycodes'), ...); }. Unlike sensitive fields such as password/passwordhash, which are excluded from AugmentedUser entirely, twofactorrecoverycodes is neither excluded from augmentation nor present in Statamic's Antlers variable guard lists (guardedVariablePatterns/guardedContentVariablePatterns in src/Providers/ViewServiceProvider.php, and the runtime GlobalRuntimeState guard paths), which by default only guard config.app.key. On any Antlers template field where raw/dynamic template rendering is enabled for a given field (an admin/developer-configured, blueprint-level field option), a template such as {{ currentuser.twofactorrecoverycodes }}{{ value }}|{{…

Published by the source

5 Aug 2026, 15:32 UTC

Last modified by the source

1 Sep 2026, 20:10 UTC

Source last checked

26 Oct 2026, 14:51 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jppw-r5j3-xf7x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jppw-r5j3-xf7x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71293

Advisory: Statamic CMS exposes two-factor recovery codes through dynamic Antlers rendering
IDs: CVE-2026-71293, GHSA-jppw-r5j3-xf7x
Record: https://patchnext.com/advisories/cve-2026-71293 (revision 2, source checked 26 Oct 2026, 14:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist statamic/cms: affected >= 6.0.0-alpha.1, <= 6.30.0

## Suggested inspection (read-only)
- Packagist statamic/cms: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on statamic/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jppw-r5j3-xf7x (OSV record GHSA-jppw-r5j3-xf7x lists affected ranges: Packagist statamic/cms >=6.0.0-alpha.1 <=6.30.0)
- Verified: https://github.com/advisories/GHSA-jppw-r5j3-xf7x (GitHub-reviewed advisory GHSA-jppw-r5j3-xf7x lists affected ranges: Packagist statamic/cms >=6.0.0-alpha.1 <=6.30.0)

Commands are suggestions: review each one before running it.