Skip to content
Applications

CVE-2026-72824

9.3
Critical
EPSS 0.40%Patch availableAug 14, 2026

Grav API plugin scope-bypass enables Twig SSTI and remote code execution

common questions

Is CVE-2026-72824 being exploited?

Not confirmed. CVE-2026-72824 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.40% probability of exploitation in the next 30 days.

How severe is CVE-2026-72824?

CVE-2026-72824 is rated Critical with a CVSS score of 9.3. 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-72824?

Yes. A fix has been recorded for CVE-2026-72824. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72824 affect?

CVE-2026-72824 affects getgrav/grav-plugin-api <1.0.13, Grav CMS with security.twig_content.process_enabled=true, Sites using API keys minted on super accounts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72824?

Upgrade to >=1.0.13; revoke/reissue super-account API keys; disable Twig processing if possible

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
getgrav/grav-plugin-api <1.0.13Grav CMS with security.twig_content.process_enabled=trueSites using API keys minted on super accounts
impact

API-key scope bypass lets Twig execute on page save, causing server-side template injection and remote code execution as the server user.

action required

Immediate action required

affected versions
getgrav grav
  • affected< 1.0.13
vendor says fixed in1.0.13

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free