Vulnerability · Published Aug 25, 2026 · Assigned by VulnCheck

CVE-2026-72700Grav before 3.9.1 Timing Attack via Non-Constant-Time Token Comparison

High 7.5

In plain English

A high-severity security flaw in grav from getgrav. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 38% of all known vulnerabilities).

Severity (CVSS 3.1)7.5High

Exploit odds (30 days)0.4%top 62.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official description

The getgrav/grav-plugin-login Composer plugin before 3.9.1 (used by Grav) compares password reset and account activation tokens using a non-constant-time === string comparison instead of hash_equals() in classes/Controller.php (taskReset()) and login.php (activation handler). Because the token-submission endpoint (taskReset) also lacks rate limiting, an attacker could in principle send repeated token guesses against a known username and use the timing differences to attempt to recover a valid token, though the vendor rates the practical exploitability as low and no end-to-end network exploit has been demonstrated.

Affected products (as reported)

Vendor	Product	Versions
getgrav	grav	0 – before 3.9.1

Weakness: CWE-208 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

GitHub Security Advisory (GHSA-x239-6jqx-5hjh) vendor-advisory
VulnCheck Advisory: Grav before 3.9.1 Timing Attack via Non-Constant-Time Token Comparison third-party-advisory