CVE
Grav authorization bypass in Flex Pages storage
Only affects Grav 2.0.0 through 2.2.17 sites that use the Flex Objects plugin, per-page permissions, and a front-end Flex pages form. Fixed in Grav 2.2.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.2.18.
Summary
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.
Who should check
Teams running Grav 2.0.0 through 2.2.17 with per-page permissions and the Flex Objects plugin's front-end pages form, where publishers edit pages
“Grav 2.x from 2.0.0 up to and including 2.2.17”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade 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-130733 (Grav 2.0.0 before 2.2.18 Authorization Bypass via Flex Pages Storage), 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-130733 (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.x from 2.0.0 up to and including 2.2.17 (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rxf-jpgc-hwpv)
- Flex Objects plugin enabled (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rxf-jpgc-hwpv)
- Site relies on per-page permissions (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rxf-jpgc-hwpv)
- A front-end Flex pages form placed on a page (source: https://github.com/getgrav/grav/security/advisories/GHSA-3rxf-jpgc-hwpv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130733 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130733 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-3rxf-jpgc-hwpv
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-130733
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-130733"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
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-3rxf-jpgc-hwpv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130733 |
| Record | NVD · CVE-2026-130733 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130733
Is CVE-2026-130733 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 can overwrite or delete pages that the site's permissions deny them. They can also gain access to the protected subtree by replacing the permissions block.Source: github.com
Which versions are affected by CVE-2026-130733?
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 up to and including 2.2.17 is affected when the Flex Objects plugin is enabled, the site relies on per-page permissions, and a front-end Flex pages form is placed on a page. To check, compare your Grav version against that range and look for the Flex Objects plugin, per-page permissions, and any front-end Flex pages form.Source: github.com
How do I fix CVE-2026-130733?
Upgrade Grav to 2.2.18 or later, which is the fixed version.Source: github.com