CVE-2026-100667
MEDIUMDescription
grav-plugin-login (the Grav CMS Login plugin) versions >= 3.8.7 and < 3.9.7 allow the two-factor authentication challenge to be bypassed for content gated by the authenticated() Twig function or the [authenticated] shortcode. On sites with 2FA enabled, Login::isAuthenticated() checked only the session flag indicating that the password step had succeeded, not the flag indicating that login had completed, so a session sitting at the 2FA code prompt was treated as fully authenticated. An attacker who knows a member's password but cannot answer that member's second factor can therefore read member-only content rendered by the no-argument authenticated() or group authenticated(null, 'group') forms and by [authenticated]; the inverse [guest] shortcode is likewise evaluated too early. Impact is limited to disclosure of that content: the attacker does not obtain a completed session, cannot access pages protected by an access: rule, and cannot act as the user. The authenticated('some.permission') form, which goes through UserObject::authorize(), is not affected. Fixed in grav-plugin-login 3.9.7.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 22% of all known CVEs.
References
Related Vulnerabilities
Other CWE-304 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-54391 | Critical | 9.8 | 3.2% | - | - |
| CVE-2022-1065 | High | 8.1 | 2.9% | - | Fix |
| CVE-2026-55957 | High | 7.3 | 2.9% | - | Fix |
| CVE-2022-2302 | Critical | 9.8 | 2.1% | - | Fix |
| CVE-2024-2172 | Critical | 9.8 | 1.7% | - | - |
| CVE-2019-16766 | High | 8.7 | 1.5% | - | Fix |
Common questions
How do I fix CVE-2026-100667?
No published fix for CVE-2026-100667 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-100667 being actively exploited?
Not that we know of. CVE-2026-100667 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.31% is the estimated probability that it will be exploited in the next 30 days. That is higher than 22% of all scored CVEs.
How severe is CVE-2026-100667?
CVE-2026-100667 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-100667
Markdown
[](https://tridentstack.com/cve/CVE-2026-100667)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100667"><img src="https://tridentstack.com/cve/badge/CVE-2026-100667.svg" alt="CVE-2026-100667"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-28.