External risk intelligence

Grav Group Access Field Privilege Escalation.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-75837

Grav is a content management system typically deployed as a public-facing web application. Since the vulnerability involves escalating privileges within the administrative interface, which is a common component of web-based CMS deployments, it is likely to be exposed to the internet in many standard configurations.

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 concerns a vulnerability in the Grav content management system that could allow a lower-privileged administrator to gain full super-admin control. This escalation grants the ability to execute code and modify system settings, potentially impacting the integrity and availability of the system. The main concern is confirming relevance and exposure to your specific Grav instances.

  • Admin users can gain full control.
  • Leads to potential system compromise.
  • Confirm Grav instances and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by leveraging an existing administrative account with limited user management privileges. By manipulating the group access settings, an attacker can escalate their privileges to super-admin, granting them control over the system's scheduler and the ability to execute Twig code. This could ultimately lead to full system compromise.

  • Attacker needs admin access.
  • Manipulate group access field.
  • Full system compromise.

Live Threat

Current exploitation, exposure, and threat context

A delegated administrator could potentially gain full super-admin privileges, enabling them to execute scheduler tasks and evaluate Twig code. This escalation is possible when the access field in the core group blueprint is not adequately protected, and a user with `admin.users` operator rights saves a group with `access[admin][super]=true`.

  • Super-admin capabilities and Twig evaluation.
  • Delegated admin saves a group with elevated access.
  • Unauthorized system control and code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Grav, a content management system. Given its typical deployment as a public-facing web application, the first practical step is to identify all Grav instances, assess their exposure and criticality, and confirm their accountable owners. This will inform a risk-based remediation plan, potentially involving vendor coordination or temporary risk reduction measures.

  • Application owners should own the issue.
  • Verify Grav instance exposure and 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 content management system (CMS) that does not require a database. It is widely used by developers and content creators to build flexible, high-performance websites. Because it is flat-file, it is often chosen for simplicity and speed, serving as the foundation for various web applications where administrators manage content, users, and system settings through a built-in web interface.

What does CWE-269 mean for CVE-2026-75837?

CWE-269 refers to Improper Privilege Management. In the context of this CVE, it means the software fails to properly verify or restrict permissions when a user modifies group settings. Specifically, the system incorrectly trusts input regarding access levels, allowing a user who should have limited rights to grant themselves 'super-admin' status, thereby bypassing the intended security boundaries of the administrative dashboard.

Can this vulnerability be triggered by a guest user?

No, this vulnerability cannot be triggered by a standard site visitor or guest. It requires an existing user account that already possesses delegated 'admin.users' operator privileges. The trigger involves a specific action within the administrative interface—specifically, saving a modified group configuration—meaning an attacker must already have a foothold with administrative management rights to initiate the escalation.

Why does Halo Surface Signal categorize this as likely exposed?

Halo Surface Signal flags this as likely exposed because Grav is typically deployed as a public-facing web application. Since the administrative interface is a core component of how these sites are managed, it is frequently reachable via the internet. If your Grav instance is accessible to the public, the risk is higher because the administrative panel itself may be reachable, potentially widening the window for an internal user to exploit these settings.

How should I respond if I am running Grav?

Begin by auditing your current Grav environment to verify which instances are active and who is responsible for their maintenance. Because this issue concerns elevated user privileges, focus on reviewing existing administrative accounts and their assigned roles. Once you have an inventory, prepare to apply the necessary software updates from the vendor to secure the group access blueprints and restore proper authorization controls.

References