CVE
Grav stored XSS via Twig injection in media metadata
Affects Grav 2.0.0 through 2.2.17 with Page Twig enabled and a public upload form on a page that also shows another medium with a link, lightbox or thumbnail. Fixed in Grav 2.2.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
Grav from 2.0.0 before 2.2.18 contains a Twig injection vulnerability that allows media-only accounts and anonymous uploaders to execute Twig by placing delimiters in image titles, alt text, class, id, or file names. Attackers can combine injected Twig with the autoescape tag to serve script to every page visitor, including super admins, or expose unpublished page content.
Who should check
Teams running Grav 2.0.0 through 2.2.17 that allow media uploads, media-only API accounts, or public upload forms on pages showing linked or thumbnail media
“Grav 2.x from 2.0.0 up to and including 2.2.17”
cve.now Index
- Exploitation0/40No signal
- Exposure25/25Default setups, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade 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-130735 (Grav 2.0.0 before 2.2.18 Twig Injection via Media Metadata and File Names), 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-130735 (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.0.0 through 2.2.17 (source: https://github.com/getgrav/grav/security/advisories/GHSA-jc8q-6vcj-4x25)
- Page Twig enabled, which is on by default for pages since Grav 2.0.19 (source: https://github.com/getgrav/grav/security/advisories/GHSA-jc8q-6vcj-4x25)
- Public upload form with a file field, on a page that also shows another medium with a link, lightbox or thumbnail option (source: https://github.com/getgrav/grav/security/advisories/GHSA-jc8q-6vcj-4x25)
- auto_metadata_exif enabled, which is off by default (source: https://github.com/getgrav/grav/security/advisories/GHSA-jc8q-6vcj-4x25)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130735 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130735 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-jc8q-6vcj-4x25
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-130735
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-130735"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · 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-jc8q-6vcj-4x25 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130735 |
| Record | NVD · CVE-2026-130735 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130735
Is CVE-2026-130735 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?
Media metadata and file names can inject Twig template code into Grav pages. The injected script is served to every page visitor, including super admins, which can lead to a super-admin session, and unpublished page content can also be exposed.Source: github.com
Which versions are affected by CVE-2026-130735?
grav: from 2.0.0 before 2.2.18.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.0.0 through 2.2.17 is affected when Page Twig is enabled, which is on by default for pages since Grav 2.0.19, and a public upload form with a file field sits on a page that also shows another medium with ?link, ?lightbox or ?display=thumbnail. Anonymous uploads are also covered when auto_metadata_exif is enabled, which is off by default. To check, look at the installed Grav version and the auto_metadata_exif and Page Twig settings.Source: github.com
How do I fix CVE-2026-130735?
Upgrade Grav to 2.2.18, the fixed version. The facts name no separate vendor patch ids for this issue.Source: github.com