Skip to main content
Vulnerability Database/CVE-2026-109314

CVE-2026-109314: Grav Login Plugin Information Disclosure

CVE-2026-109314 is an information disclosure flaw in Grav Login plugin that allows publishers to steal password-reset tokens and take over privileged accounts. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-109314 Overview

CVE-2026-109314 is an information disclosure vulnerability [CWE-200] in the Grav Login plugin, affecting versions 1.2.0 through versions before 3.9.9. A publisher-level user can author a page at the password-reset route. When a victim clicks an emailed reset link, the attacker-controlled page rendered by Login::getPage() captures the username and bearer token embedded in the URL. The attacker then uses those values to complete the reset flow and take over higher-privileged accounts, including administrators.

Critical Impact

Authenticated publishers can harvest password-reset tokens for other users and hijack more privileged accounts, including Grav administrators.

Affected Products

  • Grav CMS Login plugin version 1.2.0 and later
  • Grav CMS Login plugin versions prior to 3.9.9
  • Grav installations granting publisher-level page authoring to untrusted users

Discovery Timeline

  • 2026-10-12 - CVE-2026-109314 published to the National Vulnerability Database
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2026-109314

Vulnerability Analysis

The Grav Login plugin uses a configurable route to render the password-reset form. The plugin resolves this route through Login::getPage(), which returns whatever page object exists at that URL path. The function does not verify that the page originates from the plugin's own template or that the resolver has produced a trusted system page.

A user with publisher privileges can create a Grav page whose slug matches the reset route. Grav's page resolution favors the authored content, so that page renders when victims follow their emailed reset link. The URL contains the reset token and username as query parameters or path segments. The publisher-controlled Twig template receives those values through the normal Grav request context and can log, display, or exfiltrate them.

Because the stolen token is valid for the account that requested the reset, the attacker can complete the password change and seize the target account. Administrators and other elevated roles become reachable from a lower-privilege publisher account.

Root Cause

The root cause is an unsafe trust boundary in page resolution for a security-sensitive route. Login::getPage() does not enforce that the reset endpoint can only be served by plugin-provided templates, allowing user-authored content to shadow a system page.

Attack Vector

Exploitation requires an authenticated publisher account and user interaction from the victim, who must open the emailed reset link. The attacker publishes a page at the reset route, triggers or waits for a password reset against a privileged account, and reads the token from the attacker-controlled render context.

No exploit code is required beyond an authored Grav page template. See the GitHub Security Advisory GHSA-277m-9x28-gjq2 and the VulnCheck Advisory for Grav Plugin for additional technical context.

Detection Methods for CVE-2026-109314

Indicators of Compromise

  • Grav pages authored at or near the configured reset route, especially by non-admin accounts
  • Unexpected Twig templates rendering request parameters named token, user, or similar reset fields
  • Password-reset events for administrator accounts closely followed by successful logins from new IP addresses or user agents

Detection Strategies

  • Audit the Grav pages/ tree for any content whose slug matches the Login plugin's route_reset configuration value
  • Review Grav user roles and identify publisher accounts that have created or modified pages after installing the Login plugin
  • Correlate web server access logs for requests to the reset route against the authenticated user that owns the rendered page

Monitoring Recommendations

  • Alert on page creation events whose slug equals the configured password-reset route
  • Monitor outbound HTTP requests from the Grav host that include values resembling reset tokens or usernames
  • Track administrator password resets and flag any that occur without a corresponding help-desk or self-service ticket

How to Mitigate CVE-2026-109314

Immediate Actions Required

  • Upgrade the Grav Login plugin to version 3.9.9 or later on all Grav installations
  • Invalidate any outstanding password-reset tokens and force a password reset for administrator accounts
  • Review publisher-authored content and remove any pages that shadow authentication routes

Patch Information

The maintainers fixed the issue in Grav Login plugin version 3.9.9. Upgrade through Grav's plugin manager with bin/gpm update login or by replacing the plugin directory with the patched release referenced in GHSA-277m-9x28-gjq2.

Workarounds

  • Restrict publisher permissions so untrusted editors cannot create or modify top-level pages
  • Change the Login plugin's route_reset value to a non-guessable path and keep the new route confidential
  • Delete or quarantine any existing page whose slug matches the current reset route until the plugin is upgraded
bash
# Update the Grav Login plugin to the patched release
cd /path/to/grav
bin/gpm update login
bin/gpm versions login

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.