CVERadar
CRITICAL · CVSS 4.0 9.3EPSS n/aThreat level 47

CVE-2026-130733: CVE-2026-130733: Grav from 2.0.0 before 2.2.18 contains an authorization bypass vulnerability that allows p…

Unknown · Grav · NVD published 2026-11-18 · posted 2026-11-18 · last modified 2026-11-18

CVE-2026-130733 at a glance

CVE-2026-130733 is a critical-severity vulnerability in Grav, with a CVSS 4.0 base score of 9.3. NVD published it on 2026-11-18 and classifies the weakness as CWE-140. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 47/100.

What it is

Grav from 2.0.0 before 2.2.18 contains an authorization bypass vulnerability that allows publishers to overwrite pages their per-page permissions deny by abusing FolderStorage key delimiter collisions and PageStorage folder reconstruction. Attackers can rename a folder like locked*** or save from a page with an unusual prefix width through a front-end Flex pages form, replacing protected content and permissions to access the protected subtree.

WeaknessCWE-140 definition
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (source: VulnCheck)
ATT&CK tacticsn/a

No ATT&CK techniques could be mapped or inferred for this CVE yet.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources