dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-61454

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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
The Grav Admin2 plugin (getgrav/grav-plugin-admin2) before 2.0.4 embeds a global JavaScript variable window.__GRAV_CONFIG__ in the Admin2 SPA bootstrap page at /grav/admin (and its subroutes). This object is returned in every unauthenticated response and discloses the server URL, API prefix, admin base path, runtime environment type, and exact Grav and Admin2 version numbers, allowing an unauthenticated attacker to fingerprint the deployment and select version-specific exploits without reconnaissance.

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 · high confidence

The Grav Admin2 plugin before version 2.0.4 exposes a JavaScript configuration object (window.__GRAV_CONFIG__) in the unauthenticated bootstrap response at /grav/admin, disclosing server URL, API prefix, admin base path, runtime environment, and exact version numbers for both Grav CMS and the Admin2 plugin.

MitigationUpgrade the Admin2 plugin to version 2.0.4 or later, or restrict unauthenticated access to the /grav/admin endpoint via web server authentication or firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Admin2 plugin version
    Locate the Admin2 plugin in your Grav installation (typically in /user/plugins/ or /plugins/ directory) and check the version specified in the plugin's manifest or version file
    Affected if The installed version is lower than 2.0.4 (e.g., 2.0.3, 2.0.2, etc.)
  2. Test unauthenticated access to admin endpoint
    Send an HTTP GET request to /grav/admin (or /admin) without providing any authentication credentials and observe the response
    Affected if The endpoint responds with HTTP 200 and returns a page intended for authenticated users, indicating the page is accessible without login
  3. Inspect response for exposed configuration
    Examine the HTML/JavaScript response from the /grav/admin endpoint and search for the string 'window.__GRAV_CONFIG__' or '__GRAV_CONFIG__'
    Affected if The response contains a JavaScript object named __GRAV_CONFIG__ with properties such as base_url, api_prefix, admin_route, environment, and version numbers for Grav CMS and the Admin2 plugin
  4. Review disclosed version information
    Parse the __GRAV_CONFIG__ object (if present) and extract the version values from the 'version' or similar fields within the configuration object
    Affected if The exposed version numbers correspond to an Admin2 plugin version below 2.0.4

You are affected if the Admin2 plugin version is below 2.0.4 AND the /grav/admin endpoint is accessible without authentication and returns the __GRAV_CONFIG__ object containing sensitive version and configuration details.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Admin2 plugin to version 2.0.4 or later, or restrict unauthenticated access to the /grav/admin endpoint via web server authentication or firewall rules.

Recommended fix Moderate confidence

2.0.4

  1. Identify the Grav Admin2 plugin (getgrav/grav-plugin-admin2) in the installation
  2. Determine the currently installed version of the Admin2 plugin
  3. Upgrade the Admin2 plugin to version 2.0.4 or later
  4. Clear the Grav cache to ensure the updated configuration is loaded
  5. Verify that unauthenticated requests to /grav/admin (and subroutes) no longer expose the window.__GRAV_CONFIG__ variable with sensitive information

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61454 — 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-2026-61454 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