CVE
Grav remote code execution via Markdown image URL media actions
Affects Grav 2.0.0 up to and including 2.2.17 via Markdown image URL media actions. Fixed in 2.2.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Grav 2.x from 2.0.0 up to and including 2.2.17
Summary
Grav from 2.0.0 before 2.2.18 contains a remote code execution vulnerability that allows publishers to bypass the media action allowlist using scoped method names in Markdown image URLs. Attackers can chain actions like self::addMetaFile into static calls such as Process::fromShellCommandline to read files and run shell commands as the web server user.
Who should check
Teams running Grav 2.x CMS sites with page editor (publisher) accounts; sites where a public form mails fields through the Email plugin with process_markdown enabled are also exposed to anonymous visitors.
Not fixed by: The publisher route has no configuration workaround.
“Grav 2.x from 2.0.0 up to and including 2.2.17”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Grav 2.x from 2.0.0 up to and including 2.2.17Upgrade to a fixed version: 2.2.18.
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-130736 (Grav 2.0.0 before 2.2.18 RCE via Markdown Image URL Media Actions), 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-130736 (entry last updated 2026-11-18):
Affected:
- getgrav grav: from 2.0.0, fixed in 2.2.18
Fixed versions: 2.2.18.
Conditions (all must be true for the bug to be hit):
- Grav 2.x from 2.0.0 up to and including 2.2.17 (source: https://github.com/getgrav/grav/security/advisories/GHSA-fhg3-xwwr-cq26)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130736 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130736 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-fhg3-xwwr-cq26
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-130736
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-130736"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- getgrav grav
From 2.0.0 · fixed in 2.2.18
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · getgrav/grav · Advisory GHSA-fhg3-xwwr-cq26 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130736 |
| Record | NVD · CVE-2026-130736 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130736
Is CVE-2026-130736 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 publisher can read files and run code as the web server user, which gives full control of the site and the server account.Source: github.com
Which versions are affected by CVE-2026-130736?
grav: from 2.0.0 before 2.2.18.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.x from 2.0.0 up to and including 2.2.17 is in scope. Check the installed Grav version to see whether it falls in that range.Source: github.com
How do I fix CVE-2026-130736?
Upgrade to Grav 2.2.18, the first fixed version.Source: github.com