CVE-2026-130733 is a critical authorization bypass in Grav 2.0.0 up to but not including 2.2.18. According to the NVD description, it can let publishers overwrite pages that their per-page permissions should block.
What Is It
The vulnerability is in how Grav handles page storage. According to the NVD description, publishers can abuse key delimiter collisions in FolderStorage and the way PageStorage reconstructs folders. This lets them overwrite pages that their per-page permissions deny.
The record names two attack methods. Both are carried out through a front-end Flex pages form:
- renaming a folder to something like
locked*** - saving from a page that has an unusual prefix width
According to the advisory, either method can replace protected content and permissions, which could give the attacker access to the protected subtree. The weakness is classed as CWE-140 (Improper Neutralization of Delimiters).
Why It Matters
VulnCheck, the CNA, rates this flaw as critical:
- CVSS 3.1: 9.8 CRITICAL (
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) - CVSS 4.0: 9.3 CRITICAL
Both vectors describe a network attack with low complexity and no user interaction. They rate the impact on confidentiality, integrity and availability as high. The vectors say no privileges are required, but the written description says the attacker is a publisher. Given that conflict, defenders may want to treat this as a flaw that could break the per-page permission boundaries between accounts that can edit content.
No CISA KEV entry was supplied for this CVE, so CISA has not confirmed active exploitation. NVD lists the record as "Deferred," and the CVSS 4.0 exploit maturity is "Not Defined."
What's Vulnerable
| Vendor | Product | Affected | Unaffected |
|---|---|---|---|
| getgrav | grav | 2.0.0 up to but not including 2.2.18 | 2.2.18 |
Grav sites that use per-page permissions to restrict publisher accounts and also expose front-end Flex pages forms are likely to face the most risk.
Patch Status
The affected-version data lists Grav 2.2.18 as unaffected. Administrators running Grav 2.0.0 through 2.2.17 should upgrade to 2.2.18 or later. There is no KEV entry, so the source data gives no CISA-mandated deadline for fixing it. The GitHub security advisory listed below has the vendor's details.
Until the upgrade is done, check which accounts hold publisher rights. Also review protected page subtrees for unexpected changes to content or permissions.