PatchSiren cyber security CVE debrief
CVE-2026-72699 getgrav CVE debrief
The Grav Login plugin (getgrav/grav-plugin-login) before version 3.9.1 is vulnerable to email address enumeration. This vulnerability arises from the register() method in classes/Login.php, which throws a distinct exception (EMAIL_NOT_AVAILABLE) when a submitted email address already belongs to an existing account. The lack of rate limiting on the registration endpoint allows an attacker to enumerate which email addresses have accounts on the site, one guess per request. Administrators and users of the Grav Login plugin, especially those with publicly accessible registration endpoints, should be aware of this vulnerability and take steps to mitigate it. The CVE record was published on 2026-08-25T02:16:45.687Z and has not been modified since then.
- Vendor
- getgrav
- Product
- grav-plugin-login
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-25
- Original CVE updated
- 2026-08-29
- Advisory published
- 2026-08-25
- Advisory updated
- 2026-08-29
Who should care
Administrators and users of the Grav Login plugin, especially those with publicly accessible registration endpoints, should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and updating their current security measures to prevent potential enumeration of email addresses associated with existing accounts.
Technical summary
The Grav Login plugin (getgrav/grav-plugin-login) before version 3.9.1 is vulnerable to email address enumeration due to the register() method in classes/Login.php throwing a distinct exception when a submitted email address already belongs to an existing account. The registration endpoint lacks rate limiting, allowing an attacker to enumerate email addresses with one guess per request. This vulnerability can be mitigated by patching the plugin to version 3.9.1 or later and implementing rate limiting on the registration endpoint.
Defensive priority
Defenders should prioritize patching the Grav Login plugin to prevent potential enumeration of email addresses associated with existing accounts.
Recommended defensive actions
- Patch the Grav Login plugin to version 3.9.1 or later
- Implement rate limiting on the registration endpoint
- Monitor for suspicious registration activity
- Consider using a Web Application Firewall (WAF) to detect and prevent exploitation
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE-2026-72699 record indicates that the Grav Login plugin is vulnerable to email address enumeration due to the register() method in classes/Login.php throwing a distinct exception when a submitted email address already belongs to an existing account. The registration endpoint lacks rate limiting, allowing an attacker to enumerate email addresses with one guess per request. Official sources include the CVE Program and NVD.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72699 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72699
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72699 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72699
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/getgrav/grav/security/advisories/GHSA-crh8-xm27-j9g9
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/grav-login-plugin-before-email-enumeration-via-registration
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.