Grav remote code execution in API plugin blueprint upload
Affects the getgrav/grav-plugin-api Grav API plugin versions 1.0.0 through 1.1.3, where publisher accounts with api.media.write and api.pages.write rights can write files into the active theme's Twig templates. Fixed in 1.1.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.1.4
- Who is exposed
- Specific setups only
Summary
The Grav API plugin for the getgrav Grav product has a remote code execution flaw that lets an attacker with low-privilege login, specifically publisher rights with media and page write access, exploit it over the network. Through the blueprint-upload endpoint, the attacker can write a file into a theme's Twig templates folder, include it from sandboxed page Twig, and run commands as the web-server user.
Written by a model
Original description
Grav API plugin from 1.0.0 before 1.1.4 contains a remote code execution vulnerability that allows publishers with media and page write rights to write theme template files through the blueprint-upload endpoint. Attackers can upload a file into a theme's Twig templates folder and include it from sandboxed page Twig to execute commands as the web-server user.
Who should check
Teams running Grav CMS with the getgrav/grav-plugin-api plugin, versions 1.0.0 through 1.1.3, where publishers have media or page write rights.
“getgrav/grav-plugin-api 1.0.0 through 1.1.3”
What to do
Check whether your setup matches what the bug needs.
Grav API plugin (getgrav/grav-plugin-api) version 1.0.0 through 1.1.3 Attacker account with api.media.write and api.pages.write rights Form plugin with a form process: message action in page frontmatter as the confirmed triggerUpgrade to a fixed version: 1.1.4.
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-134253 (Grav API Plugin 1.0.0 before 1.1.4 RCE via blueprint-upload Theme Template Write), 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-134253 (entry last updated 2026-11-21):
Affected:
- getgrav grav: from 1.0.0, fixed in 1.1.4
Fixed versions: 1.1.4.
Conditions (all must be true for the bug to be hit):
- Grav API plugin (getgrav/grav-plugin-api) version 1.0.0 through 1.1.3 (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rqp-8h7g-xxv8)
- Attacker account with api.media.write and api.pages.write rights (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rqp-8h7g-xxv8)
- Form plugin with a form process: message action in page frontmatter as the confirmed trigger (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rqp-8h7g-xxv8)
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-134253 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134253 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-3rqp-8h7g-xxv8
- https://www.vulncheck.com/advisories/grav-api-plugin-1.0.0-before-1.1.4-rce-via-blueprint-upload-theme-template-write
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-134253
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-134253"}.Affected versions
- getgrav gravFrom 1.0.0 · fixed in 1.1.4
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
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 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-3rqp-8h7g-xxv8 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134253 |
| Record | NVD · CVE-2026-134253 |
| Other links 1 | |
| Link | vulncheck.com · advisories/grav-api-plugin-1.0.0-before-1.1.4-rce-via-blueprint-upload-theme-template-write |
Questions about CVE-2026-134253
Is CVE-2026-134253 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?
The plugin lets a user with media and page write rights place files into the active theme's Twig template folder. The Form plugin renders a form process: message action in page frontmatter as sandboxed Twig, and an attacker can use this to run commands on the server as the web-server user. From there they could read the API signing secret and password hashes, create a super-admin account, or change site files.
Source: github.com
Which versions are affected by CVE-2026-134253?
grav: from 1.0.0 before 1.1.4.
Source: cve.now feed data
Am I affected, and how do I check?
Grav API plugin (getgrav/grav-plugin-api) versions 1.0.0 through 1.1.3 are in scope. The setup also involves an account with api.media.write and api.pages.write rights and the Form plugin with a form process: message action in page frontmatter. Check the installed getgrav/grav-plugin-api version and the account's API rights to see how this applies to a given installation.
Source: github.com
How do I fix CVE-2026-134253?
Upgrade the Grav API plugin (getgrav/grav-plugin-api) to version 1.1.4 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-130749Grav 2.0.0 before 2.2.18 Unbounded Cache Growth via Host Header
- CVE-2026-130748Grav from 2.0.0 before 2.2.18 Password Reset Poisoning via CloudFront-Forwarded-Proto
No corrections so far. Something wrong on this page? Report an error.