External risk intelligence

Grav Authorization Bypass Allows Page Overwrites

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130733

Grav is a content management system commonly deployed as a public-facing web application. The vulnerability is exploitable via a front-end form, which is a standard, internet-accessible component of web-based deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in Grav that could allow unauthorized users to overwrite protected content by manipulating folder and page storage. This issue arises from specific technical details related to how the system handles file naming and organization, potentially enabling access to restricted areas of the platform. The main concern is confirming whether our organization uses the affected technology and if it is exposed externally.

  • Unauthorized content overwriting is possible.
  • Confirms relevance and potential exposure of our systems.
  • Assess if this technology is in use and exposed.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this by leveraging weaknesses in how the system handles file storage. By specifically naming a folder with a prefix like "locked***" or by uploading a page with an unusual width, an attacker can trick the system into overwriting existing pages and their permissions. This allows them to bypass access controls and gain unauthorized entry into restricted sections of the application.

  • Requires no prior authentication.
  • Abuses folder naming and page saving.
  • Leads to unauthorized content access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to bypass page permissions and overwrite existing content on a Grav CMS site when specific conditions related to folder and page storage are met. This could lead to the replacement of protected content and permissions.

  • Protected page content and permissions.
  • Abusing folder storage key delimiters.
  • Unauthorized content modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

The authorization bypass vulnerability in Grav affects its FolderStorage and PageStorage mechanisms, allowing unauthorized page overwrites. System owners should prioritize identifying all Grav instances, assessing their reachability and criticality, and determining the accountable application or platform teams. Remediation planning must consider these factors to mitigate risk effectively.

  • Identify Grav instances and owners.
  • Verify reachability and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Grav, and how is it used?

Grav is a file-based, open-source content management system (CMS) that requires no database. It is widely used by developers and content creators to build flexible, high-performance websites. Because it stores page content and metadata in structured file folders, it provides an intuitive way to manage site hierarchies, which is the specific mechanism involved in this vulnerability.

What kind of weakness causes CVE-2026-130733?

This vulnerability is classified as CWE-140, which relates to the improper handling of neutralization of improper input during integration. In plain terms, the system fails to correctly validate or sanitize how it interprets specific folder names and page data. This allows the application to be tricked into confusing one folder or page path with another, effectively bypassing authorization rules designed to protect restricted content.

How can an attacker trigger this vulnerability?

An attacker triggers this by interacting with a public-facing Flex pages form to submit specially crafted input, such as filenames containing specific delimiters or unusual prefix widths. These inputs exploit logic gaps in the system's folder and page storage reconstruction process. Standard, non-malicious content submissions through these forms do not trigger the issue; the bypass specifically requires inputs designed to cause folder key collisions.

Do I need to worry if my Grav instance is internal?

Halo Surface Signal indicates that while this is a critical issue, the risk profile changes based on your deployment. Because the vulnerability is exploitable via a front-end form, instances that are publicly accessible on the internet are at higher risk. If your instance is strictly internal and not reachable by unauthorized users, the immediate risk of exploitation is significantly lower.

What is the first step to address this issue?

Your priority should be to catalog all Grav instances running within your environment to determine which ones are affected by the specified version range. Once identified, evaluate whether these instances are exposed to external traffic. Finally, coordinate with the teams responsible for these specific sites to schedule updates or implement access controls while preparing for the vendor's provided fix.

References