External risk intelligence

Grav Login Plugin Privilege Escalation Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-56710

The vulnerability exists in a plugin for Grav, a web application frequently deployed as an internet-facing CMS. As it involves API and administrative functionality within a web-based platform, it is 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

A security issue has been identified in a plugin for the Grav content management system that could allow an unauthorized attacker to bypass login protections on the most privileged accounts. This bypass is possible without needing the same level of access as an administrator, potentially weakening the security of critical accounts.

  • Login protections bypassed on high-privilege accounts.
  • Risk to critical administrative account security.
  • Confirm relevance and exposure to protect accounts.

Attack Path

How an attacker could exploit the issue

An attacker can bypass brute-force protections on high-privilege accounts. This is achieved by an attacker who has permission to write to user data, and can then manipulate login lockout counters for administrative accounts.

  • Attacker needs user write permissions.
  • Attacker triggers unlock handler in API.
  • Removes brute-force protection for admins.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker with `api.users.write` permission could potentially remove brute-force protections from administrative accounts by clearing their login lockout counters, bypassing the need for equivalent privileges.

  • Admin accounts are at risk.
  • Attackers could bypass lockout counters.
  • Unprotected admin accounts may be compromised.

Operational Fix

Recommended remediation, mitigation, and detection steps

To address this critical vulnerability in the Grav Login plugin, application owners and platform teams are likely responsible for remediation. The immediate first step is to identify all instances of the affected Grav installation, determine their exposure (internal/external), confirm business criticality, and then assign ownership for a coordinated response, potentially involving vendor coordination if the plugin is managed externally.

  • Own the issue and scope exposure.
  • Verify affected Grav instances and reachability.
  • Plan and coordinate remediation efforts.

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 the Grav Login plugin?

Grav is a file-based content management system (CMS) used to build websites without a traditional database. The Login plugin adds authentication features to Grav, allowing site administrators to manage user access, sessions, and security protections like login lockout counters to prevent brute-force attacks against the platform.

What does CWE-863 mean for CVE-2026-56710?

CWE-863 refers to Incorrect Authorization. In the context of this CVE, it means the software fails to verify if a user has the appropriate permission level before executing a specific action. Here, the plugin allows a lower-privileged user to interact with administrative account settings that they should not have the authority to access.

How is this vulnerability triggered?

An attacker triggers this issue by using the 'onApiUserListRowAction' unlock handler within the plugin. To do this, the attacker must already possess 'api.users.write' permissions. The vulnerability is not triggered by users lacking this specific API write access, nor can it be initiated through standard, unauthenticated guest interactions.

Is my Grav instance relevant to this CVE?

According to Halo Surface Signal, this vulnerability is highly relevant because Grav is typically deployed as an internet-facing CMS. If your Grav instance is reachable from the public internet, the API functionality affected by this flaw is likely exposed to remote attackers, necessitating a prompt review of your deployment's security posture.

What should I do to secure my system?

Your first step is to audit your Grav installations to confirm if the Login plugin is active and in use. Determine which instances are internet-facing versus those restricted to internal networks. Once identified, coordinate with your team to verify the plugin version and prioritize updating to version 1.0.16 or later to resolve the underlying authorization flaw.

References