Authentication Bypass in getgrav/grav (CVE-2026-62669)
Summary
Authentication bypass in getgrav/grav (CVE-2026-62669). Confidential information can be exposed externally. Exploitable via login.regenerate2FASecret. Mitigation: upgrade to 2.0.4 or later.
Original description
The description as published by the source.
Grav Login Plugin adds login, basic ACL, and session wide messages to Grav. Prior to 3.8.11, the Grav Login plugin login.regenerate2FASecret task checks only that the pending-session user exists rather than requiring $user->authorized. After submitting a victim's correct password, an attacker can invoke taskRegenerate2FASecret() during the pending TOTP challenge, overwrite twofa_secret, read the replacement secret from the response, calculate a valid code, and complete authentication without the victim's second factor. This issue is fixed in version 3.8.11.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62669 has been found in getgrav/grav.
Attackers can target a specific entry point like login.regenerate2FASecret over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade getgrav/grav to 2.0.4 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-62669" on the vendor's site.
CVE-2026-62669 (getgrav/grav) — CWE-287 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: login.regenerate2FASecret / twofa_secret / taskRegenerate2FASecret / twofa_cancel
Patched: 2.0.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in getgrav/grav. Attackers reach the vulnerable code path via login.regenerate2FASecret without authentication.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: login.regenerate2FASecret / twofa_secret / taskRegenerate2FASecret / twofa_cancel.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 2.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'getgrav/grav' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'getgrav/grav' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
getgrav/gravを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade getgrav/grav to 2.0.4ステージング環境で 2.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com
- web github.com