CVE-2026-62236: Cross-Site Request Forgery (CSRF) in getgrav grav
A Cross-Site Request Forgery (CSRF) vulnerability exists in grav-plugin-login versions before 3.8.11. The vulnerability affects the login.regenerate2FASecret frontend task, allowing an attacker to force a logged-in user to regenerate their TOTP secret without proper CSRF protections. This causes the victim's two-factor authentication to become invalid, forcing re-enrollment. The issue does not affect sites configured with session.samesite set to Strict. The vulnerability has a low severity score.
AI Analysis
Technical Summary
The grav-plugin-login component of the Grav CMS before version 3.8.11 contains a CSRF vulnerability in the login.regenerate2FASecret frontend task. This task regenerates and persists a new TOTP secret for the authenticated user session but lacks anti-CSRF nonce or Origin/Referer validation. Because the task is dispatched via a GET 'task:' URI parameter and the default session cookie uses SameSite=Lax, an attacker can trick a logged-in user into visiting an off-site page that triggers a GET request to rotate the victim's TOTP secret. This invalidates the victim's current authenticator setup, forcing them to re-enroll in 2FA. Sites with session.samesite configured as Strict are not vulnerable.
Potential Impact
An attacker can cause a logged-in user to unknowingly regenerate their TOTP secret, invalidating their current two-factor authentication setup. This disrupts the user's ability to authenticate using 2FA until they complete re-enrollment. The vulnerability does not allow direct account takeover or credential theft but can cause denial of service to 2FA-protected accounts.
Mitigation Recommendations
A fix is available in grav-plugin-login version 3.8.11 and later. Users should upgrade to version 3.8.11 or newer to remediate this vulnerability. Alternatively, configuring the site to use session.samesite: Strict mitigates the issue by preventing the CSRF attack vector. No other mitigations are indicated.
CVE-2026-62236: Cross-Site Request Forgery (CSRF) in getgrav grav
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in grav-plugin-login versions before 3.8.11. The vulnerability affects the login.regenerate2FASecret frontend task, allowing an attacker to force a logged-in user to regenerate their TOTP secret without proper CSRF protections. This causes the victim's two-factor authentication to become invalid, forcing re-enrollment. The issue does not affect sites configured with session.samesite set to Strict. The vulnerability has a low severity score.
CVSS v4.0
Score 2.3low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The grav-plugin-login component of the Grav CMS before version 3.8.11 contains a CSRF vulnerability in the login.regenerate2FASecret frontend task. This task regenerates and persists a new TOTP secret for the authenticated user session but lacks anti-CSRF nonce or Origin/Referer validation. Because the task is dispatched via a GET 'task:' URI parameter and the default session cookie uses SameSite=Lax, an attacker can trick a logged-in user into visiting an off-site page that triggers a GET request to rotate the victim's TOTP secret. This invalidates the victim's current authenticator setup, forcing them to re-enroll in 2FA. Sites with session.samesite configured as Strict are not vulnerable.
Potential Impact
An attacker can cause a logged-in user to unknowingly regenerate their TOTP secret, invalidating their current two-factor authentication setup. This disrupts the user's ability to authenticate using 2FA until they complete re-enrollment. The vulnerability does not allow direct account takeover or credential theft but can cause denial of service to 2FA-protected accounts.
Mitigation Recommendations
A fix is available in grav-plugin-login version 3.8.11 and later. Users should upgrade to version 3.8.11 or newer to remediate this vulnerability. Alternatively, configuring the site to use session.samesite: Strict mitigates the issue by preventing the CSRF attack vector. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-13T16:41:09.007Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59784168715ace4305da72
Added to database: 07/17/2026, 00:33:05 UTC
Last enriched: 07/17/2026, 00:48:22 UTC
Last updated: 07/17/2026, 00:48:22 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.