CVE-2026-72700
Timing attack on Grav login plugin may expose reset/activation tokens.
Is CVE-2026-72700 being exploited?
Not confirmed. CVE-2026-72700 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-72700?
CVE-2026-72700 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72700?
Yes. A fix has been recorded for CVE-2026-72700. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72700 affect?
CVE-2026-72700 affects getgrav/grav-plugin-login <3.9.1, Grav CMS sites using the plugin, taskReset token endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72700?
Upgrade to plugin v3.9.1; add rate limiting/WAF and monitor auth logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can use timing differences to recover reset/activation tokens and reset accounts or takeover user accounts.
Patch when possible
- affected< 3.9.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.