dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-65897

HIGH · 8.8 CVSS v3.1 Published 2026-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 4 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
Grav API Plugin versions before 1.0.10 fail to validate the groups field in InvitationsController::create(), allowing authenticated api.users.write callers to assign invited accounts to groups that grant api.super permissions. Attackers can create invitation records with elevated group membership, and when accepted, the new account gains full super-admin API access without the inviter holding those permissions.

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 versions before 1.0.10 lack authorization validation on the groups field in InvitationsController::create(). Authenticated users with api.users.write permissions can assign invited accounts to privileged groups (including api.super), enabling privilege escalation when the invitation is accepted.

MitigationUpgrade to Grav API Plugin version 1.0.10 or later which implements proper group assignment validation. Alternatively, implement authorization checks ensuring users can only assign groups they themselves possess.

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
High

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

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. Identify Grav API Plugin installation and version
    Locate the Grav API Plugin directory (commonly at /user/plugins/api or /plugins/api) and check the version in the plugin's manifest or version file. Compare against the fixed version 1.0.10.
    Affected if The installed version is lower than 1.0.10 or the version cannot be determined.
  2. Enumerate users with api.users.write permission
    Query the Grav user accounts database or configuration files (typically in /user/config/permissions.yaml or per-user YAML files in /user/accounts/) for any user account possessing the 'api.users.write' permission attribute.
    Affected if Any user account other than the primary super-admin has the api.users.write permission assigned.
  3. Review pending or recent invitations for elevated group assignments
    Inspect the invitations storage (commonly in /user/data/invitations or database-backed invitation records) and look for invitation records where the 'groups' field includes any group granting 'api.super' or equivalent super-admin API privileges.
    Affected if There exists an invitation (pending or accepted) that specifies a group containing api.super permissions.
  4. Audit newly created user accounts with super-admin API access
    Review all user accounts in /user/accounts/ (or database user table) and identify accounts that have 'api.super' permission. Cross-reference account creation dates to determine if any were created via the invitation system after the plugin was installed.
    Affected if There are user accounts with api.super permission that were created via invitation and the inviter does not themselves possess api.super privileges.
  5. Examine API audit logs for invitation creation requests
    Check Grav's API request logs (typically in /logs/ or a dedicated api-access log file) for POST requests to the invitations endpoint, inspecting the request payload for the 'groups' parameter and whether it contains elevated permissions beyond what the requesting user holds.
    Affected if Logs show invitation creation requests where the groups field contains api.super or similar elevated permissions.

A user is affected if the Grav API Plugin version is below 1.0.10 AND any non-super-admin user possesses api.users.write permission, or if invitation records exist that grant api.super privileges to accounts whose creator does not hold those privileges.

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 to Grav API Plugin version 1.0.10 or later which implements proper group assignment validation. Alternatively, implement authorization checks ensuring users can only assign groups they themselves possess.

Recommended fix Moderate confidence

Grav API Plugin version 1.0.10

  1. Log in to the Grav admin panel as an administrator
  2. Navigate to the Plugins section
  3. Locate the Grav API Plugin
  4. Check the current version - if below 1.0.10, an update is needed
  5. Use the built-in plugin update mechanism to upgrade to version 1.0.10
  6. Alternatively, via command line: run `bin/gpm install grav-api-plugin` or `bin/gpm update grav-api-plugin`
  7. After upgrading, verify the new version is 1.0.10 in the plugins list
  8. Test that the API invitation functionality works correctly with proper permission enforcement

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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