Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocate public registration endpoint
-
DeliverySubmit candidate email addresses
-
ExploitObserve EMAIL_NOT_AVAILABLE discrepancy
-
ExecutionEnumerate valid accounts unthrottled
-
ImpactFeed list to phishing/credential-stuffing
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication Timing-safe comparisons
|
| Exploitation Conditions | Exploitation requires that the Grav site has the Login plugin (before 3.9.1) installed with public self-registration enabled and reachable, which is the specific deployment mode where the register() endpoint is exposed to unauthenticated users. The concrete oracle is the distinct EMAIL_NOT_AVAILABLE exception returned for already-registered addresses versus normal progression for new ones, and the enabling factor is the absence of rate limiting on that endpoint. Limiting factors: if open registration is disabled, gated behind admin approval, or protected by an external rate-limiter/CAPTCHA/WAF, the enumeration oracle is unavailable or throttled; the vulnerability discloses only account existence and grants no access to the accounts themselves. |
| Impact | The signals here conflict sharply and must be read critically. The provided CVSS 4.0 vector claims high confidentiality, integrity, AND availability impact (VC:H/VI:H/VA:H) for a score of 9.3, but the underlying weakness is email enumeration - an information-disclosure issue that in reality has at most limited confidentiality impact and no integrity or availability impact. This is a case of high-CVSS-but-low-real-risk: the numeric severity does not match the described behavior, and defenders should not treat this as a critical RCE-class issue. Genuine risk factors are that exploitation is network-reachable, unauthenticated (PR:N), low-complexity, and requires no user interaction, so enumeration itself is trivial and automatable. However, no EPSS score, KEV listing, POC, or SSVC data was provided, and there is no public exploit identified. The practical impact is reconnaissance - harvesting valid account emails to feed phishing, credential-stuffing, or password-spray campaigns - not direct compromise of the host. |
| Exploit ScenarioDerived | An attacker scripts requests against a Grav site's public registration form, submitting a wordlist of candidate email addresses. Addresses that already have accounts return the distinct EMAIL_NOT_AVAILABLE error while unknown addresses proceed toward registration, and with no rate limiting the attacker rapidly compiles a list of valid users to target with phishing or password-spray attacks. No public POC is identified, but the technique is trivial to implement given the low attack complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Email address enumeration in the Grav Login plugin (getgrav/grav-plugin-login) before 3.9.1 lets unauthenticated remote attackers determine which email addresses are registered on a Grav CMS site. The register() method returns a distinct EMAIL_NOT_AVAILABLE error for already-registered addresses while proceeding normally otherwise, and because the registration endpoint enforces no rate limiting, an attacker can test addresses at scale, one per request. No public exploit identified at time of analysis; the assigned CVSS 4.0 score of 9.3 appears substantially inflated for what is fundamentally an information-disclosure weakness.
RemediationAI
Vendor-released patch: upgrade the Grav Login plugin to version 3.9.1 or later, which is the primary and authoritative fix per advisory GHSA-crh8-xm27-j9g9. If an immediate upgrade is not possible, apply compensating controls: add rate limiting or CAPTCHA to the registration endpoint to blunt automated enumeration (trade-off: adds friction to legitimate sign-ups), and where feasible normalize registration responses so that existing and non-existing emails return an identical generic message and require email-confirmation before revealing account state (trade-off: changes the user-facing registration flow). Disabling open self-registration entirely eliminates the oracle if public registration is not a business requirement. Reference the vendor advisory (https://github.com/getgrav/grav/security/advisories/GHSA-crh8-xm27-j9g9) and VulnCheck writeup (https://www.vulncheck.com/advisories/grav-login-plugin-before-email-enumeration-via-registration) for details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Grav is a PHP-based flat-file CMS, and its Login plugin provides user registration and authentication. The root cause is CWE-203 (Observable Discrepancy): the register() routine in classes/Login.php distinguishes the 'email already in use' state by throwing a unique EMAIL_NOT_AVAILABLE exception, producing an observable difference in server behavior between existing and non-existing accounts. Combined with the absence of rate limiting on the registration endpoint, this discrepancy becomes a reliable enumeration oracle. The affected component per CPE is getgrav:grav (all versions listed), with the vulnerable code residing specifically in the Login plugin prior to 3.9.1.
Know when Grav gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Unauthenticated network enumeration with no user interaction gives AV:N/AC:L/PR:N/UI:N; impact is limited account-existence disclosure so C:L and I:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
The Grav Login plugin (getgrav/grav-plugin-login) before 3.9.1 is vulnerable to email address enumeration. The register() method in classes/Login.php throws a distinct exception (EMAIL_NOT_AVAILABLE) when a submitted email address already belongs to an existing account, while allowing registration to proceed otherwise. Because the registration endpoint has no rate limiting, an attacker can enumerate which email addresses have accounts on the site, one guess per request.
Executive ViewAI
Grav Login plugin versions before 3.9.1 contain an unauthenticated email enumeration vulnerability enabling attackers to harvest registered user email addresses at scale. Organizations using affected Grav CMS instances face direct risk of phishing, credential stuffing, and account targeting attacks. With no rate limiting on the registration endpoint, attackers can automate reconnaissance to build organizational user rosters, significantly lowering barriers to initial compromise.
Apply rate limiting (5 requests per IP/minute) to registration endpoints; deploy WAF rules to detect and block enumeration attempts; mask registration error messages to return identical responses for all input states; implement CAPTCHA on authentication forms; enable login anomaly detection; consider temporarily restricting public registration to authenticated users if operationally viable; monitor for coordinated registration failures indicating active enumeration campaigns.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Grav Login Plugin Authorization and Timing Flaws
View all 3Server-side template injection (SSTI) in Grav (getgrav/grav) prior to 1.8.0-beta.27 allows an authenticated attacker hol
Broken access control in Grav CMS (CWE-285) before 1.8.0-beta.27 lets an authenticated editor-level user escalate their
A Remote Code Execution (RCE) vulnerability in Grav CMS v1.7.48 allows an authenticated admin to upload a malicious plug
Grav is a file-based Web platform. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low a
GravCMS 1.10.7 allows unauthenticated remote attackers to write arbitrary YAML configuration files, leading to full serv
Remote code execution in Grav CMS 2.0.4 (fixed in 2.0.7) lets an authenticated user holding the admin.pages or api.pages
Remote code execution in Grav CMS before 2.0.15 allows attackers holding page-edit or blueprint-config privileges to wri
Vertical privilege escalation in Grav CMS before 2.0.14 lets a delegated administrator holding only the admin.users perm
Stored cross-site scripting in Grav CMS before 2.0.15 lets authenticated editors smuggle JavaScript event handlers past
Server-side request forgery (SSRF) in Grav CMS versions prior to 1.7.49.5 allows remote authenticated attackers to make
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, Grav CMS is vulnerable to a Server-Side Template Injection (S
Remote code execution in Grav CMS before 2.0.13 allows authenticated low-privilege users to plant and execute arbitrary
EUVD-2026-65213
GHSA-55hc-4r2f-h6wr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB