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.
CVE-2026-72700
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026Grav before 3.9.1 Timing Attack via Non-Constant-Time Token Comparison | Advisories | VulnCheck
https://www.vulncheck.com/advisories/grav-before-timing-attack-via-non-constant-time-token-comparisonPassword reset and activation tokens compared with non-constant-time === instead of hash_equals(), and reset-submission endpoint has no rate limiting · Advisory · getgrav/grav · GitHub
https://github.com/getgrav/grav/security/advisories/GHSA-x239-6jqx-5hjhVendor Advisories for CVE-2026-72700(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 06:45 UTCGHSA enrichment
- 2026-08-25 18:29 UTCEG score recompute
- 2026-08-25 18:28 UTCGHSA enrichment
- 2026-08-25 17:41 UTCEG score recompute
- 2026-08-25 17:41 UTCGHSA enrichment
- 2026-08-25 14:36 UTCEG score recompute
- 2026-08-25 14:36 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-72700?
When was CVE-2026-72700 disclosed?
Is CVE-2026-72700 actively exploited?
What is the CVSS score of CVE-2026-72700?
How do I remediate CVE-2026-72700?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72700
Is Your Infrastructure Affected by CVE-2026-72700?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.