GHSA-jppw-r5j3-xf7x
Suggest an improvement- Source
- https://github.com/advisories/GHSA-jppw-r5j3-xf7x
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/08/GHSA-jppw-r5j3-xf7x/GHSA-jppw-r5j3-xf7x.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-jppw-r5j3-xf7x
- Aliases
-
- CVE-2026-71293
- Published
- 2026-08-05T15:32:21Z
- Modified
- 2026-09-01T20:10:46Z
- Severity
-
- 6.2 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N CVSS Calculator
- 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_codeshandle 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. - Database specific
{ "cwe_ids": [ "CWE-200", "CWE-522" ], "github_reviewed": true, "github_reviewed_at": "2026-09-01T19:56:31Z", "nvd_published_at": "2026-08-05T13:24:54Z", "severity": "MODERATE" }- References
Affected packages
Packagist / statamic/cms
Package
- Name
- statamic/cms
- Purl
- pkg:composer/statamic/cms