On this page (8 sections)

A critical flaw tracked as CVE-2026-130733 affects the Grav flat-file CMS. According to the GitHub Advisory Database entry, Grav from 2.0.0 before 2.2.18 contains an authorization bypass that lets users with publisher rights overwrite pages that their per-page permissions deny.

If you run Grav 2.x with multiple editors, a protected section of the site, or front-end Flex pages forms, this is worth your attention today. The entry was published on November 18, 2026, and the description implies the fix is in release 2.2.18.

What happened

The advisory describes an authorization bypass involving Grav's FolderStorage and PageStorage components. A publisher can overwrite pages that their per-page permissions explicitly deny. The overwrite can replace both the protected content and the permissions that guard the protected subtree.

The same text appears on NVD, but NVD repeats the GitHub wording and is not independent confirmation. At the time of writing, only this one advisory entry covers the issue, and it is marked as unreviewed with no package listed. The entry also links to a project advisory (GHSA-3rxf-jpgc-hwpv), but its content was not available to us, so everything below comes from the database description alone and has not been reproduced by us.

Technical details in plain terms

The advisory attributes the flaw to FolderStorage key delimiter collisions and PageStorage folder reconstruction. According to the entry, an attacker can abuse this in two ways, both through a front-end Flex pages form:

  • Rename a folder to something like locked*** so that it collides with a protected page.
  • Save from a page with an unusual prefix width.

The weakness class is CWE-140, improper neutralization of delimiters. As a plain-language interpretation that the sources do not spell out: characters in folder names appear to be treated as delimiters, which can make the system confuse which page is being written, so the permission rules for the protected page are bypassed. This is a logic flaw in access control rather than a classic injection. We are deliberately not describing exact requests.

How serious is it, and a discrepancy to note

The advisory lists a CVSS v4 base score of 9.3, with network attack vector, low complexity, no user interaction, and high impact on confidentiality, integrity and availability of the vulnerable system. The same metrics list Privileges Required as None. The description, however, speaks of publishers, which implies an authenticated account. The sources do not explain this difference. Until it is clarified, assume that an attacker needs at least a publisher-level account, but do not rely on that to delay patching.

CVSS v4 base score (GitHub advisory)
9.3
Release the description implies as the fix
2.2.18
First affected version
2.0.0

Who is exposed

You are most likely affected if all of these apply:

  • You run Grav from 2.0.0 up to, but not including, 2.2.18.
  • You use per-page permissions to keep some pages or subtrees restricted from certain users.
  • You give people publisher access, or expose Flex pages forms on the front end.

A single-author site with no restricted pages and no front-end forms has a smaller practical exposure, but should still upgrade. Agencies hosting many Grav sites for clients should check each installation, since versions often differ between sites.

How to check your exposure

The advisory lists affected and patched versions as unknown in its structured fields, so rely on the version range in the description. Start with your installed version, which the Grav admin panel shows on its dashboard, and compare it with the range 2.0.0 to before 2.2.18.

Then look for signs of misuse. The sources give no indicators of compromise, so these are general review steps:

  • List which pages use restrictive per-page permissions and confirm their content and permission settings still match what you expect.
  • Look for folders with unexpected names, especially ones containing repeated special characters such as asterisks.
  • Review recent changes by publisher accounts to protected sections, using file modification times or your version control history if the site is tracked in git.
  • Check which front-end Flex pages forms are reachable and by whom.

What to do now

  1. Upgrade Grav to 2.2.18 or later, following the official Grav update process, after taking a backup.
  2. Confirm the new version in the admin panel once the update completes.
  3. Audit publisher accounts: remove unused ones and reduce rights to what each person needs.
  4. Restore any protected page whose content or permissions changed unexpectedly from a known good backup or git history.
  5. If you cannot upgrade immediately, consider disabling or restricting access to front-end Flex pages forms until you can. The advisory names these forms as the attack path, but it does not list an official workaround, so verify this on a staging copy first.
  6. Rotate credentials for any publisher account you suspect was misused.
Caution. Take a full backup of the site files and content before upgrading, and test the update on a staging copy where possible. Confirm your pages and permissions look correct afterwards.

Detection and monitoring afterwards

Authorization bugs leave little trace in outside scans, because the damage is changed content and permissions rather than a visible exploit. Keep the site's content under version control or regular backups so that unexpected edits to protected pages can be spotted and reverted. Watch web server logs for POST requests to Flex pages form endpoints from accounts that should not be editing those sections.

For the outside view, Webforta Monitor can alert you to certificate, DNS and header changes, and our guide on checking if a website is hacked covers what to look for if you suspect tampering. Our website hacked checklist explains the recovery steps.

What we do not know yet

  • Whether the flaw is being exploited. The sources do not say, and no CISA KEV entry is listed.
  • Whether a public proof of concept exists. Nothing in the sources mentions one.
  • The exact privileges needed, given the mismatch between the description and the metrics.
  • Whether versions before 2.0.0 are affected. The description only covers 2.0.0 up to 2.2.18.
  • What the linked project advisory (GHSA-3rxf-jpgc-hwpv) says. Its content was not available to us.
Check the project's own advisory and release notes for any workaround or additional detail before making decisions, since this article relies on a single unreviewed database entry.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130733 - GitHub Advisory Databasegithub.com
  2. CVE-2026-130733: 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…nvd.nist.gov ·
  • Grav
  • CVE-2026-130733
  • authorization bypass
  • CMS security
  • Flex pages