Summary
Grav Admin Plugin vulnerable to User Enumeration & Email Disclosure
Impact
- Severity: Medium
- Type: Information Disclosure / User Enumeration
- Who is Impacted: All Grav sites using Admin plugin v1.10.49.1 with password reset enabled.
- Risks:
- Allows attackers to enumerate valid usernames.
- Exposes email addresses of admin accounts, which can be used in:
- Credential stuffing
- Password spraying
- Phishing/social engineering campaigns
- Further exploitation in combination with other vulnerabilities
CVE-2025-66307 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.0-beta.27); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Modify the
taskForgot()logic to always return a generic, non-identifying message, regardless of whether the username exists or rate limits are hit.Example safe response:
If the account exists, password reset instructions will be sent.Do not include email addresses ($to) or other sensitive data in error messages.
Frequently Asked Questions
- What is CVE-2025-66307? CVE-2025-66307 is a medium-severity security vulnerability in getgrav/grav (composer), affecting versions < 1.8.0-beta.27. It is fixed in 1.8.0-beta.27.
- How severe is CVE-2025-66307? CVE-2025-66307 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of getgrav/grav are affected by CVE-2025-66307? getgrav/grav (composer) versions < 1.8.0-beta.27 is affected.
- Is there a fix for CVE-2025-66307? Yes. CVE-2025-66307 is fixed in 1.8.0-beta.27. Upgrade to this version or later.
- Is CVE-2025-66307 exploitable, and should I be worried? Whether CVE-2025-66307 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-66307 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-66307? Upgrade
getgrav/gravto 1.8.0-beta.27 or later.