CVE-2026-72700

published 25 Aug 2026 · updated 25 Aug 2026

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

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.9.1.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
getgrav<3.9.13.9.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-72700 severity on Zeptric[![CVE-2026-72700](https://zeptric.io/badge/cve/CVE-2026-72700.svg)](https://zeptric.io/cve/CVE-2026-72700)