CVE-2026-71293: Statamic/cms Statamic CMS Exposes Two-factor Recovery Vulnerability
MODERATECVE-2026-71293 is a MODERATE (CVSS 6.2) statamic cms exposes two-factor recovery vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Statamic/cms libraries in the Packagist ecosystem. The issue involves statamic cms exposes two-factor recovery codes through dynamic antlers rendering. Remediation is available in the latest vendor maintenance releases.
CVE-2026-71293 at a Glance
Security Impact
CVSS: 6.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N).
How to Fix CVE-2026-71293
To remediate this vulnerability, upgrade all affected Statamic/cms dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade statamic/cms to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for statamic/cms
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-71293, inspect your project dependencies for Statamic/cms:
inspect dependencies for statamic/cms
Analyze the terminal output to locate any version of Statamic/cms in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Statamic/cms, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-71293 Affected Statamic/cms Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
statamic/cms
|
Packagist |
≥ 6.0.0-alpha.1
≤ 6.30.0
|
|
References
Frequently Asked Questions
What is CVE-2026-71293?
Which Statamic/cms versions are affected?
What version fixes CVE-2026-71293?
Is statamic/cms affected?
What is the CVSS score of CVE-2026-71293?
What CWE is associated with CVE-2026-71293?
How can I check Packagist dependencies for CVE-2026-71293?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jppw-r5j3-xf7x",
"modified" : "2026-09-01T19:56:31Z",
"published" : "2026-08-05T15:32:21Z",
"aliases" : [ "CVE-2026-71293" ],
"summary" : "Statamic CMS exposes two-factor recovery codes through dynamic Antlers rendering",
"details" : "Statamic CMS's user-augmentation resolver, AugmentedUser::get() in src/Auth/AugmentedUser.php, contains an explicit case for the `two_factor_recovery_codes` handle that returns the user's raw two-factor recovery codes with no access restriction: `if ($handle === 'two_factor_recovery_codes') { return new Value($this->data->get('two_factor_recovery_codes'), ...); }`. Unlike sensitive fields such as password/password_hash, which are excluded from AugmentedUser entirely, two_factor_recovery_codes 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 `{{ current_user.two_factor_recovery_codes }}{{ value }}|{{ /current_user.two_factor_recovery_codes }}` renders the viewing user's own 2FA recovery codes directly into the HTML response, allowing an attacker who can view or capture that response (e.g. via a shared/observable page, or a crafted link causing a victim to render it) to obtain the codes and bypass 2FA. Exploitation requires that dynamic Antlers rendering already be enabled on a field the target user's data flows through, which is a blueprint-configuration privilege rather than a standard content-editing permission.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "statamic/cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "6.0.0-alpha.1"
}, {
"last_affected" : "6.30.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-71293"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/statamic/cms"
}, {
"type" : "WEB",
"url" : "https://github.com/statamic/cms/blob/master/src/Auth/AugmentedUser.php"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-522" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-01T19:56:31Z",
"nvd_published_at" : "2026-08-05T13:24:54Z"
}
}