dbcve.org
Grav Plugin AdminPlugin / extension · Getgrav

CVE-2025-66307

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-01
Fix available
A fix is available. Upgrade to after 1.10.50 or later.
See remediation →
62/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This admin plugin for Grav is an HTML user interface that provides a convenient way to configure Grav and easily create and modify pages. Prior to 1.11.0-beta.1, a user enumeration and email disclosure vulnerability exists in Grav. The "Forgot Password" functionality at /admin/forgot leaks information about valid usernames and their associated email addresses through distinct server responses. This allows an attacker to enumerate users and disclose sensitive email addresses, which can be leveraged for targeted attacks such as password spraying, phishing, or social engineering. This vulnerability is fixed in 1.11.0-beta.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Grav Plugin AdminPlugin / extension
Affected:<= 1.10.50

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.10.50
Vendor patch github.com →
Recommended fix High confidence

1.11.0-beta.1

  1. 1. Backup your Grav installation and database before proceeding with any upgrade.
  2. 2. Navigate to your Grav project's root directory.
  3. 3. Update the Grav Plugin Admin package using your package manager (e.g., composer or the Grav CLI). For Composer-based installations: `composer update getgrav/grav-plugin-admin` to version 1.11.0-beta.1 or later.
  4. 4. Alternatively, if using Grav's GPM (Grav Package Manager), run: `bin/gpm install admin` to fetch the latest version.
  5. 5. Verify the installed version by checking the plugin's `blueprints.yaml` or `admin.yaml` file to confirm version 1.11.0-beta.1 or higher is installed.
  6. 6. Test the 'Forgot Password' functionality at /admin/forgot to confirm the vulnerability is remediated - the system should now return consistent responses for both valid and invalid usernames.
  7. 7. Clear any caches: `bin/grav clear-cache`.
Caveat beta releases may contain new features or changes; test in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data