CVE-2026-109312 — Grav Login Plugin 2.7.0 before 3.9.9 2FA Bypass via Profile Update Form

Grav Login plugin 2.7.0 before 3.9.9 contains an authentication bypass in processUserProfile(), which checks that the session user exists but not that a pending front-end 2FA session is fully authorized. Attackers with a victim's password who can publish a page form without an access rule can invoke update_user before completing 2FA to disable twofa_enabled and take over the account.

Published Oct 12, 2026Updated Oct 12, 2026Sources: cvelistV5, VulnCheck

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

getgrav

grav_plugin_login

CVSS base

8.1

HIGH

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

getgrav

Products (1)

grav plugin login

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.1	CVSS 3.1	HIGH	—	—	cvelistV5

Weakness & attack patterns

CWE-287

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1548Abuse Elevation Control Mechanism
T1040Network Sniffing
T1185Browser Session Hijacking

References

2 on the record

github.com/getgrav/grav/security/advisories/GHSA-5rph-jqcf-2x36
vendor-advisory, third-party-advisory
www.vulncheck.com/advisories/grav-login-plugin-2.7.0-before-3.9.9-2fa-bypass-via-profile-update-form
third-party-advisory

Elsewhere on this site

getgravevery CVE for this vendor
CWE-287other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.