External risk intelligence

Grav Allowlist Bypass Allows Arbitrary Method Execution

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-112780

Grav is a web application (CMS) typically deployed as a public-facing web site. While the vulnerability requires page-edit permissions, the application itself is fundamentally designed to be an internet-facing web service, making the attack surface commonly exposed to the public internet in standard 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

This advisory details a critical vulnerability in Grav's Flex form functionality, enabling unauthorized users with editing permissions to execute arbitrary code by manipulating form field names. This could lead to the deletion or overwriting of files and directories on affected systems.

  • Allows unauthorized code execution through form manipulation.
  • Critical vulnerability impacting file integrity and system access.
  • Confirm relevance and exposure of affected Grav instances.

Attack Path

How an attacker could exploit the issue

An attacker could start with an account that has page-editing permissions on a Grav website. By manipulating Flex form fields, the attacker can bypass security checks and execute arbitrary public static methods. This allows them to perform actions like deleting directories, overwriting files, or reading sensitive files on the server.

  • Requires page editor permissions.
  • Trick form processor to call methods.
  • Delete files, overwrite, or read data.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in Grav could allow authenticated users with page-edit permissions to invoke arbitrary public static methods. This could lead to the deletion or modification of files and directories on the server.

  • Server files and directories could be affected.
  • Maliciously crafted form field names could be used.
  • Unauthorized file deletion or reading may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Grav installations with administrative or page-editing access. The first step is to identify all Grav instances, determine their exposure and criticality, and pinpoint the accountable application or platform owner. Remediation planning should then proceed based on assessed risk.

  • Application owners should manage the issue.
  • Verify administrative access and exposure.
  • Plan and schedule updates or vendor coordination.

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 flat-file content management system (CMS) built on PHP. Unlike traditional database-driven systems, it stores content and configuration directly in file structures. Users typically leverage Grav to build fast, flexible websites, using its Flex form features to collect user data or manage site content through an administrative interface.

What is the vulnerability in CVE-2026-112780?

This vulnerability is an allowlist bypass, categorized as CWE-749: Exposed Dangerous Method or Function. In Grav, the system is designed to only allow specific, safe actions. However, by manipulating form field names with a special syntax, an attacker can trick the application into executing restricted public static methods that should have been blocked, leading to unauthorized file or directory operations.

How does an attacker trigger this CVE-2026-112780 flaw?

An attacker must have page-editing permissions to interact with the Flex form fields. The trigger involves injecting specific directives into the 'replace-name@' field attribute to bypass security checks. Notably, this bug is not triggered by standard site visitors who lack these elevated editor privileges; it requires an account that is already authorized to modify page content.

Is my Grav installation relevant to this threat?

According to Halo Surface Signal, Grav is commonly deployed as an internet-facing service, which places these systems in a high-visibility category. Even though the exploit requires existing editor permissions, you should consider the risk high if your instance is exposed to the public internet, as compromised editor credentials would allow an attacker to leverage this flaw to damage your server's file integrity.

What are the first steps to handle this vulnerability?

Begin by auditing your environment to locate all active Grav instances and identify who is responsible for managing them. Prioritize reviewing the security of any accounts with page-editing permissions, as these are the primary vector. Once identified, coordinate with your application owners to plan updates and ensure your installation is moved to a version where these security checks are properly enforced.

References