Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-72700 – Timing-Based Token Disclosure – Grav Login Plugin before 3.9.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-72700 is a timing-based side-channel vulnerability (CWE-208: Observable Timing Discrepancy) affecting the login plugin bundled with the Grav flat-file CMS. The plugin validates password-reset and account-activation tokens using a non-constant-time === string comparison instead of hash_equals(), and the token-submission endpoint has no rate limiting. The issue carries a CVSS v4.0 base score of 8.7 (High), though the vendor and researcher both assess practical, remote exploitability as low.

Technical details

  • Root cause: Token validation in classes/Controller.php (taskReset() method) and in the login.php account-activation handler compares submitted tokens to the expected value with PHP’s === operator rather than the constant-time hash_equals() function, which Grav already uses correctly elsewhere.
  • Trigger conditions: An attacker must repeatedly submit password-reset or account-activation tokens against the endpoint and statistically measure response timing to infer correct token characters.
  • Attack vector: Network — no authentication or user interaction required to attempt exploitation, but the endpoint’s lack of rate limiting is what would allow the volume of timing samples needed for a practical attack.
  • Impact: If successfully exploited, an attacker could recover a valid token and gain unauthorized password reset or account activation capability on a targeted account, potentially leading to account takeover. Researchers measured a 4.3% timing variance with === versus 0.0% variance for hash_equals(), but note that network jitter typically obscures such small timing signals, and no working end-to-end network exploit has been publicly demonstrated.

Affected software

  • Grav (login plugin component getgrav/grav-plugin-login), all versions through 3.9.0

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Grav to version 3.9.1 or later, which replaces the vulnerable === comparisons with hash_equals().
  • If immediate patching is not possible: Restrict or monitor access to password-reset and account-activation endpoints, apply request rate limiting at the web server or WAF layer to prevent the high-volume repeated submissions a timing attack requires, and monitor logs for unusual bursts of reset/activation attempts against the same account.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge