grav-plugin-login before 3.8.11 contains a cross-site request forgery (CSRF) vulnerability in the login.regenerate2FASecret frontend task, which regenerates and persists a new TOTP secret for the authenticated session user without any anti-CSRF nonce or Origin/Referer check. Because Grav core dispatches the task from the GET 'task:' URI parameter and the default session cookie is SameSite=Lax, an attacker can lure a logged-in victim to an off-site page that performs a top-level GET navigation, rotating the victim's TOTP secret so their enrolled authenticator no longer matches the server, effectively forcing 2FA re-enrollment. Sites configured with session.samesite: Strict are not affected.
CVE-2026-62236
Score 5.4 from GitHub Security Advisory (severity: LOW) published 2026-07-17. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 1.0%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026grav-plugin-login < 3.8.11 CSRF via regenerate2FASecret | Advisories | VulnCheck
https://www.vulncheck.com/advisories/grav-plugin-login-csrf-via-regenerate2fasecretCSRF in grav-plugin-login: anonymous attacker rotates a logged-in user's 2FA (TOTP) secret (no nonce on task=login.regenerate2FASecret) · Advisory · getgrav/grav · GitHub
https://github.com/getgrav/grav/security/advisories/GHSA-4px8-7p53-282rVendor Advisories for CVE-2026-62236(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-18 14:42 UTCEG score recompute
- 2026-07-18 14:42 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 14:51 UTCEG score recompute
- 2026-07-17 14:51 UTCGHSA enrichment
- 2026-07-17 06:53 UTCGHSA enrichment
- 2026-07-17 00:24 UTCEG score recompute
- 2026-07-17 00:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-62236?
When was CVE-2026-62236 disclosed?
Is CVE-2026-62236 actively exploited?
What is the CVSS score of CVE-2026-62236?
How do I remediate CVE-2026-62236?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62236
Is Your Infrastructure Affected by CVE-2026-62236?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.