CVE-2026-72700

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.

CVSS 4.0

8.7CVSS: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 3.1

7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

0.4% chance of exploitation in the next 30 days; higher than 37% of CVEs (scores of 2026-10-25)

CWE

CWE-208

Published

2026-08-25

Modified

2026-10-12

Record from

the NVD, synced 2026-10-19

References

• https://github.com/getgrav/grav/security/advisories/GHSA-x239-6jqx-5hjh
• https://www.vulncheck.com/advisories/grav-before-timing-attack-via-non-constant-time-token-comparison
• https://github.com/getgrav/grav/security/advisories/GHSA-x239-6jqx-5hjh

Check your stackJSON