Skip to main content
CVE-2026-130733VulnerabilityPublished

Grav from 2.0.0 before 2.2.18 contains an authorization bypass vulnerability that allows publishers to overwrite pages

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130733· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 2.2.18 as a priority.

Data as of 18 Nov 2026, 14:04 UTC

CVSS 4.0 base score
9.3Critical
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.09.3
CNA (VulnCheck)CVSS 3.19.8
Patch
Available – fixed in 2.2.18
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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 fix is available in Grav version 2.2.18. Users should upgrade to version 2.2.18 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the available data.

Description

Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain an authorization bypass vulnerability. This flaw allows users with publisher-level permissions to overwrite pages that their per-page permissions should deny. The vulnerability arises from abusing FolderStorage key delimiter collisions and PageStorage folder reconstruction, enabling attackers to rename folders or save pages with unusual prefixes via the front-end Flex pages form. This results in unauthorized replacement of protected content and permissions within the protected subtree.

References

Community reviews

Loading reviews…