External risk intelligence

Grav Authentication Bypass via Glob Pattern Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-130747

Grav is a web content management system typically deployed as a public-facing website. The vulnerability affects the setup and authentication API endpoints, which are standard web-accessible interfaces for administrative configuration in such deployments.

Authentication Bypass

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 critical vulnerability in Grav, a web content management system, allows anonymous visitors to bypass authentication and create administrator accounts due to an unescaped glob pattern. This issue, present in specific versions of Grav, could allow unauthorized individuals to gain administrative control over affected systems if their installation path contains brackets or a backslash.

  • Anonymous users can gain admin access.
  • Affects public-facing websites; critical for security.
  • Confirm relevance and exposure to affected systems.

Attack Path

How an attacker could exploit the issue

Attackers can exploit this vulnerability by accessing the Grav application through the network, specifically by sending crafted requests to its API or registration form. This allows them to bypass authentication, even on newly installed systems or those with specific path configurations, ultimately leading to the creation or overwriting of administrator accounts.

  • Unauthenticated network access required.
  • Triggered via API or registration form.
  • Risk of unauthorized administrator control.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow anonymous visitors to create or overwrite administrator accounts on affected Grav installations, particularly those with specific path configurations. This could lead to unauthorized control over the website's content and settings.

  • Unauthorized administrator account creation.
  • Exploited via API or admin registration form.
  • Full site control by attacker.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical authentication bypass vulnerability in Grav affects the core setup and administrative functionality, likely impacting platform or infrastructure teams responsible for managing the CMS. The immediate priority is to identify all Grav installations, assess their exposure and business criticality, and confirm the accountable owner before planning remediation.

  • Platform and infrastructure teams own this.
  • Verify Grav installation reachability and criticality.
  • Plan vendor coordination and remediation.

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 typically used?

Grav is a file-based, open-source web content management system (CMS) that does not require a database. Developers use it to build fast, flexible websites, ranging from simple personal blogs to complex corporate portals. Because it manages site content and settings through built-in administrative interfaces, it acts as the primary engine for creating and publishing web pages.

How does CVE-2026-130747 allow authentication bypass?

This vulnerability stems from an improper neutralization of special elements, classified as CWE-155. In affected Grav versions, the code used to count existing users fails to properly escape glob patterns. If the server's file path contains specific characters like brackets or a backslash, the check incorrectly reports zero users, tricking the system into believing it is uninitialized and allowing attackers to register a new admin account.

Does every Grav installation trigger this bug?

No. The vulnerability is specifically triggered only when the absolute file path where Grav is installed on the server contains special characters, specifically brackets ([ or ]) or a backslash (\). Installations located in paths without these characters do not trigger the faulty logic in the user-counting function, meaning they remain resilient to this specific bypass path.

Why should I care about this if my site is internal?

According to Halo Surface Signal, Grav is commonly deployed as a public-facing website, making it highly accessible to external network traffic. While internal instances may have a smaller attack surface, the vulnerability resides in the auth-setup and admin registration endpoints. If these interfaces are reachable over any network, unauthorized actors can attempt to gain full administrative control.

What are the first steps to address this Grav vulnerability?

Start by identifying all Grav instances within your infrastructure and determining if their installation directory paths contain brackets or backslashes. Prioritize updating affected systems to the versions specified in the security advisory to resolve the underlying code flaw. Ensure that administrative registration interfaces are restricted or monitored until you can apply the vendor's official patch.

References