dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-62231

HIGH · 8.1 CVSS v3.1 Published 2026-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 5 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 API plugin (getgrav/grav-plugin-api) before 1.0.6 contains an authorization bypass: API keys can be created with a restricted scopes array, but the ApiKeyAuthenticator class never reads or enforces these scopes. It loads and returns the owning user's full account object, so a key created with limited scopes (e.g. read-only) can perform any write, delete, or administrative operation the owning user is authorized for. Fixed in 1.0.6.

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 API plugin before 1.0.6 has an authorization bypass where API keys created with restricted scopes (e.g., read-only) are not enforced by the ApiKeyAuthenticator class. Instead of validating the scope array, the authenticator loads and returns the owning user's full account object, allowing a limited API key to perform any operation the user is authorized for, including write, delete, and administrative actions.

MitigationUpgrade the Grav API plugin to version 1.0.6 or later, which implements proper scope enforcement for API keys.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Locate the Grav API plugin installation
    Check for the presence of the API plugin directory, typically at /user/plugins/api/ or /plugins/api/ in the Grav installation
    Affected if The plugin directory exists and contains the ApiKeyAuthenticator class file (e.g., classes/ApiKeyAuthenticator.php)
  2. Identify the installed API plugin version
    Open the plugin manifest file (typically plugin.yaml or blueprint.yaml) in the API plugin directory and read the 'version' field
    Affected if The version is lower than 1.0.6 (e.g., 1.0.5, 1.0.4, etc.) or the version field cannot be read or is missing
  3. Verify API key authentication is configured
    Check the plugin configuration file (usually config.yaml in the API plugin folder) for the 'authentication' or 'api_key' settings and confirm 'enabled' is set to true
    Affected if API key authentication is enabled and the plugin version is below 1.0.6
  4. Check for existing API keys with scope restrictions
    Inspect the Grav system for stored API keys, typically in a data file under /user/data/ or examined via Grav admin panel under API plugin settings, noting any keys with 'scope' definitions such as read-only or limited access
    Affected if Any API keys with defined scope restrictions exist and the plugin version is below 1.0.6

The environment is affected if the Grav API plugin is installed with a version lower than 1.0.6 and API key authentication with scoped keys is in use, as the scope restrictions will not be enforced.

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 Grav API plugin to version 1.0.6 or later, which implements proper scope enforcement for API keys.

Recommended fix High confidence

grav-plugin-api version 1.0.6

  1. Check the current version of the getgrav/grav-plugin-api plugin installed on your Grav CMS instance
  2. Update the plugin to version 1.0.6 or later using Composer (composer update getgrav/grav-plugin-api) or through the Grav Admin plugin's plugin manager
  3. After updating, verify the ApiKeyAuthenticator class now properly reads and enforces the scopes array defined for each API key
  4. Test that API keys with limited scopes (e.g., read-only) can no longer perform write, delete, or administrative operations
  5. Review any existing API keys to ensure they have appropriate scopes matching their intended access level

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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