CVE
Grav code execution and file read via blueprint files
Affects Grav 2.0.0 through 2.2.17 where publishers hold page write access; the PHP execution paths also need media write access. 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.0.0 through 2.2.17 Attacker needs a publisher account with page write access; media write access is also needed for the PHP execution paths The uploaded-file blueprint path affects 2.0.15 and later
Summary
Grav from 2.0.0 before 2.2.18 contains an insecure blueprint trust vulnerability that allows publisher accounts to read secrets and execute PHP by planting or selecting attacker-controlled blueprint files. Attackers can abuse the import@ directive, uploaded YAML media named as the page template, or form.flash_folder to leak password hashes and keys or invoke static PHP methods for code execution.
Who should check
Teams running Grav 2.0.0 through 2.2.17 that let page editors or publishers edit pages and media; upgrade to 2.2.18.
“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.0.0 through 2.2.17 Attacker needs a publisher account with page write access; media write access is also needed for the PHP execution paths The uploaded-file blueprint path affects 2.0.15 and laterUpgrade 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-130743 (Grav 2.0.0 before 2.2.18 RCE and File Read via Blueprint Files), 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-130743 (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-3x2v-6jqq-7gq8)
- Attacker needs a publisher account with page write access; media write access is also needed for the PHP execution paths (source: https://github.com/getgrav/grav/security/advisories/GHSA-3x2v-6jqq-7gq8)
- The uploaded-file blueprint path affects 2.0.15 and later (source: https://github.com/getgrav/grav/security/advisories/GHSA-3x2v-6jqq-7gq8)
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-130743 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130743 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-3x2v-6jqq-7gq8
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-130743
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-130743"}.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-3x2v-6jqq-7gq8 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130743 |
| Record | NVD · CVE-2026-130743 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130743
Is CVE-2026-130743 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 account can read account password hashes and the site's secret keys, or run PHP as the web server user. Either can lead to a forged super-admin token or full control of the server account.Source: github.com
Which versions are affected by CVE-2026-130743?
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 in the affected range. The uploaded-file path, which selects a page media file as the page blueprint, was introduced in 2.0.15, so it applies to 2.0.15 and later. Compare your installed Grav version against that range.Source: github.com
How do I fix CVE-2026-130743?
Upgrade Grav to 2.2.18 or later.Source: github.com