CVE-2026-62669: CWE-287: Improper Authentication in getgrav grav
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.
AI Analysis
Technical Summary
The Grav Login plugin before version 3.8.11 contains an improper authentication vulnerability (CWE-287) in the login.regenerate2FASecret task. This task only verifies that the pending-session user exists but does not check if the user is authorized. An attacker who has correctly submitted the victim's password can invoke taskRegenerate2FASecret during the pending TOTP challenge to overwrite the twofa_secret, read the new secret from the response, compute a valid TOTP code, and bypass the second factor authentication. This allows full authentication without the victim's second factor. The vulnerability is addressed in Grav Login plugin version 3.8.11.
Potential Impact
An attacker who knows a victim's correct password can bypass the second factor of authentication, effectively defeating two-factor authentication protection. This leads to unauthorized access with high confidentiality and integrity impact, as the attacker can fully authenticate as the victim without the second factor. Availability is not impacted.
Mitigation Recommendations
This vulnerability is fixed in Grav Login plugin version 3.8.11. Users should upgrade to version 3.8.11 or later to remediate this issue. Patch status is not explicitly confirmed in the vendor advisory, but the fix version is stated. No other mitigation is indicated.
CVE-2026-62669: CWE-287: Improper Authentication in getgrav grav
Description
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.
CVSS v3.1
Score 7.4high
Affected software
pkg:github/getgrav/grav-plugin-loginRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Grav Login plugin before version 3.8.11 contains an improper authentication vulnerability (CWE-287) in the login.regenerate2FASecret task. This task only verifies that the pending-session user exists but does not check if the user is authorized. An attacker who has correctly submitted the victim's password can invoke taskRegenerate2FASecret during the pending TOTP challenge to overwrite the twofa_secret, read the new secret from the response, compute a valid TOTP code, and bypass the second factor authentication. This allows full authentication without the victim's second factor. The vulnerability is addressed in Grav Login plugin version 3.8.11.
Potential Impact
An attacker who knows a victim's correct password can bypass the second factor of authentication, effectively defeating two-factor authentication protection. This leads to unauthorized access with high confidentiality and integrity impact, as the attacker can fully authenticate as the victim without the second factor. Availability is not impacted.
Mitigation Recommendations
This vulnerability is fixed in Grav Login plugin version 3.8.11. Users should upgrade to version 3.8.11 or later to remediate this issue. Patch status is not explicitly confirmed in the vendor advisory, but the fix version is stated. No other mitigation is indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-14T20:22:04.394Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a85d17aacd9273b4948b473
Added to database: 08/19/2026, 15:53:30 UTC
Last enriched: 08/19/2026, 16:07:10 UTC
Last updated: 08/19/2026, 18:23:05 UTC
Views: 8
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.