Quick answers
- Is CVE-2026-65008 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65008 being exploited in the wild.
- How severe is CVE-2026-65008?
- Critical severity, with a CVSS score of 9.8, published 21 July 2026.
- Which products and versions are affected?
- Grav >= 2.0.4, < 2.0.7.
- Is there a fix for CVE-2026-65008?
- A patch was published on 2026-07-21: Fix released in version 2.0.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-65008 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-65008?
- Check whether you run Grav at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A remote code execution (RCE) vulnerability exists in Grav's Blueprint::dynamicData() method within system/src/Grav/Common/Data/Blueprint.php. The function passes a Class::method callable string and its arguments directly to call_user_func_array() without an allowlist. Because the Grav Form plugin routes page frontmatter through this path, an authenticated user with 'admin.pages' or 'api.pages.write' permissions can inject a malicious callable directive (such as system()) into a page's frontmatter. Once planted, the payload executes with the privileges of the web-server user whenever the page is requested, even by unauthenticated visitors. The issue is resolved in version 2.0.7.
Affected products
- getgrav Grav >= 2.0.4, < 2.0.7
Timeline
- 2026-07-07: advisory: GitHub Security Advisory published
- 2026-07-21: disclosed: CVE published to NVD
- 2026-07-21: patched: Fix released in version 2.0.7