Quick answers
- Is CVE-2026-62236 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62236 being exploited in the wild.
- How severe is CVE-2026-62236?
- Medium severity, with a CVSS score of 5.4, published 17 July 2026.
- Which products and versions are affected?
- getgrav grav-plugin-login < 3.8.11.
- Is there a fix for CVE-2026-62236?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-62236 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-62236?
- Check whether you run Grav Login Plugin. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Cross-Site Request Forgery (CSRF) vulnerability exists in the 'login.regenerate2FASecret' frontend task of the Grav Login plugin. The application fails to implement anti-CSRF nonces or Origin/Referer checks for this specific task. Because Grav dispatches tasks via GET parameters and uses 'SameSite=Lax' for session cookies by default, an attacker can trigger the secret regeneration via a top-level GET navigation (e.g., a malicious link). This overwrites the 'twofa_secret' in the user's account file, desynchronizing their authenticator app from the server. The vulnerability is patched in version 3.8.11; sites using 'session.samesite: Strict' are not affected.
Affected products
- getgrav grav-plugin-login < 3.8.11
Timeline
- 2026-06-29: advisory: GitHub Security Advisory published
- 2026-07-17: disclosed: NVD publication date