Grav authorization bypass in scoped API key checks
Affects the Grav API plugin (grav-plugin-api) 1.0.16 through 1.1.10 when a scoped API key is minted on a super-admin account. Fixed in 1.1.11.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.1.11
- Who is exposed
- Specific setups only
Summary
The Grav API Plugin for Grav (vendor getgrav) lets holders of scoped API keys override page permission rules, because access checks use the owning account's authority instead of the key's scopes. Remotely, an attacker with a low-privilege login can use keys minted on super-admin accounts to edit, delete, or read pages that deny those actions, or use media-scoped keys to change media on read-only pages.
Written by a model
Original description
Grav API plugin from 1.0.16 before 1.1.11 contains an authorization bypass vulnerability that allows scoped API key holders to override page permission rules because checks read the owning account's authority instead of the key's scopes. Attackers can use keys minted on super-admin accounts to edit, delete or read pages that deny those actions, or use media-scoped keys to change media on read-only pages.
Who should check
Teams running Grav CMS with the grav-plugin-api plugin 1.0.16 through 1.1.10, especially those issuing scoped API keys on super-admin or editor accounts.
“grav-plugin-api 1.0.16 through 1.1.10”
What to do
Check whether your setup matches what the bug needs.
Scoped API key minted on a super-admin account Affected grav-plugin-api versions 1.0.16 through 1.1.10 Media-scoped key on an account with api.pages.write, for pages whose rules don't decide update (1.1.10 only)Upgrade to a fixed version: 1.1.11.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134251 (Grav API Plugin 1.0.16 before 1.1.11 Scoped API Key Authorization Bypass), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134251 (entry last updated 2026-11-21):
Affected:
- getgrav grav: from 1.0.16, fixed in 1.1.11
Fixed versions: 1.1.11.
Conditions (all must be true for the bug to be hit):
- Scoped API key minted on a super-admin account (source: https://github.com/getgrav/grav/security/advisories/GHSA-9g3m-8mr9-78vr)
- Affected grav-plugin-api versions 1.0.16 through 1.1.10 (source: https://github.com/getgrav/grav/security/advisories/GHSA-9g3m-8mr9-78vr)
- Media-scoped key on an account with api.pages.write, for pages whose rules don't decide update (1.1.10 only) (source: https://github.com/getgrav/grav/security/advisories/GHSA-9g3m-8mr9-78vr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134251 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134251 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getgrav/grav/security/advisories/GHSA-9g3m-8mr9-78vr
- https://www.vulncheck.com/advisories/grav-api-plugin-1.0.16-before-1.1.11-scoped-api-key-authorization-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134251
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134251"}.Affected versions
- getgrav gravFrom 1.0.16 · fixed in 1.1.11
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 20 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · getgrav/grav · Advisory GHSA-9g3m-8mr9-78vr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134251 |
| Record | NVD · CVE-2026-134251 |
| Other links 1 | |
| Link | vulncheck.com · advisories/grav-api-plugin-1.0.16-before-1.1.11-scoped-api-key-authorization-bypass |
Questions about CVE-2026-134251
Is CVE-2026-134251 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A scoped API key minted on a super-admin account ignored a page's explicit deny. The key holder can act outside the key's scopes on pages whose permissions frontmatter restricts them, such as editing, deleting or reading those pages, changing page media, or writing files into page folders.
Source: github.com
Which versions are affected by CVE-2026-134251?
grav: from 1.0.16 before 1.1.11.
Source: cve.now feed data
Am I affected, and how do I check?
The bug is in grav-plugin-api versions 1.0.16 through 1.1.10. A separate case in 1.1.10 only involves a media-scoped key on an account with api.pages.write, for pages whose rules don't decide update. To check, look up the installed grav-plugin-api version in the Grav admin plugin list or the plugin's composer/package metadata.
Source: github.com
How do I fix CVE-2026-134251?
Upgrade grav-plugin-api to 1.1.11 or later, which is the fixed version.
Source: github.com
Related
- CVE-2026-130735Grav 2.0.0 before 2.2.18 Twig Injection via Media Metadata and File Names
- CVE-2026-130733Grav 2.0.0 before 2.2.18 Authorization Bypass via Flex Pages Storage
- CVE-2026-130747Grav before 1.7.53.7 and 2.x before 2.2.18 Authentication Bypass via First-Run Setup
- CVE-2026-134250Grav Form Plugin 1.1.0 before 9.1.40 Stored XSS via Unsanitized File Uploads
- CVE-2026-134253Grav API Plugin 1.0.0 before 1.1.4 RCE via blueprint-upload Theme Template Write
- CVE-2026-130749Grav 2.0.0 before 2.2.18 Unbounded Cache Growth via Host Header
No corrections so far. Something wrong on this page? Report an error.