CVE
Grav two-factor auth bypass in login plugin
Affects the Grav Login plugin up to and including 3.10.1 on Grav 2.x sites that also run the API plugin with session authentication on (the default). Fixed in 3.11.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.11.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.53% · 45th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Grav Login plugin before 3.11.0 contains an authentication bypass vulnerability that allows attackers with an account password to skip two-factor verification when the global twofa_enabled setting is off. Attackers can sign in through the /login form, remember-me cookie, or magic link to obtain a session the API plugin accepts, gaining full account permissions including super-admin control.
Who should check
Sites running Grav 2.x with grav-plugin-login up to 3.10.1 and the API plugin (bundled with Admin2 in grav-admin)
Read the source excerpt
“grav-plugin-login up to and including 3.10.1, on Grav 2.x sites that also run the API plugin”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 3.11.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126294 (Grav Login Plugin before 3.11.0 Two-Factor Authentication Bypass via /login), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126294 (entry last updated 2026-11-13):
Affected:
- getgrav grav: fixed in 3.11.0
Fixed versions: 3.11.0.
Conditions (all must be true for the bug to be hit):
- Login plugin's global twofa_enabled setting is off (the default) (source: https://github.com/getgrav/grav/security/advisories/GHSA-4x9h-4683-5fcx)
- Grav 2.x site running grav-plugin-login up to and including 3.10.1 (source: https://github.com/getgrav/grav/security/advisories/GHSA-4x9h-4683-5fcx)
- API plugin installed with session authentication enabled (source: https://github.com/getgrav/grav/security/advisories/GHSA-4x9h-4683-5fcx)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126294 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126294 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getgrav/grav/security/advisories/GHSA-4x9h-4683-5fcx
- https://www.vulncheck.com/advisories/grav-login-plugin-before-3.11.0-two-factor-authentication-bypass-via-login
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126294
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126294"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- getgrav grav
fixed in 3.11.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126294
Is CVE-2026-126294 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A login that uses only the account password can get a session with that account's full API permissions without passing its two-factor code. For an administrator account this means full control of the site.Source: github.com
Which versions are affected by CVE-2026-126294?
grav: before 3.11.0.Source: cve.now feed data
Am I affected, and how do I check?
The issue covers grav-plugin-login up to and including 3.10.1 on Grav 2.x sites that also run the API plugin with plugins.api.auth.session_enabled on (the default), while the Login plugin's global twofa_enabled setting is off (the default). To check, look at the installed Login plugin version and the API plugin's session_enabled setting.Source: github.com
How do I fix CVE-2026-126294?
Upgrade the Grav Login plugin to 3.11.0 or later.Source: github.com