Advisory record · GHSA-jppw-r5j3-xf7x

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

CVSS 6.2 MediumEPSS 0.0037 · 31st percentile

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.

PackageEcosystemAffectedFixed in
statamic/cmsPackagist>=6.0.0-alpha.1, <=6.30.0No fixed version yet
Identifiers
GHSA-jppw-r5j3-xf7x · CVE-2026-71293 · PKSA-rsd9-mj5m-pj4f
Weakness (CWE)
CWE-200 · CWE-522
Published
5 Aug 2026
Updated
1 Sept 2026

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

ScoreRatingCVSSVectorSource
6.2 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N 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

  1. 31 Oct 2026, 14:06 UTC First seen by agentprime
  2. 31 Oct 2026, 14:06 UTC Confirmed by OSV

Sources

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.