Skip to main content
CVE-2026-130743VulnerabilityPublished

Grav from 2.0.0 before 2.2.18 contains an insecure blueprint trust vulnerability that allows publisher accounts to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130743· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2.2.18 soon.

Data as of 18 Nov 2026, 14:03 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 2.2.18
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade grav to 2.2.18.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version is available starting from Grav 2.2.18. Users should upgrade to version 2.2.18 or later to remediate this vulnerability. No alternative mitigations or workarounds are specified.

Description

Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain a vulnerability involving insecure blueprint trust. This flaw allows publisher-level accounts to read sensitive secrets and execute arbitrary PHP code by manipulating blueprint files. Attackers can exploit features such as the import@ directive, specially named YAML media files, or form.flash_folder to leak password hashes, keys, or invoke static PHP methods for code execution.

References

Community reviews

Loading reviews…