Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-65008 – Remote Code Execution – Grav CMS versions prior to 2.0.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-65008 is a critical (CVSS 3.1: 9.8 / CVSS 4.0: 9.3) remote code execution vulnerability in Grav CMS affecting all versions prior to 2.0.7. The flaw resides in Blueprint::dynamicData(), which passes a Class::method callable string and its arguments directly to PHP’s call_user_func_array() without any allowlist — enabling a two-stage attack where a low-privileged authenticated user plants a malicious payload that subsequently fires for every unauthenticated visitor who loads the affected page. A patch is available in Grav 2.0.7, released on July 21, 2026.

Technical details

  • Root cause: Blueprint::dynamicData() in system/src/Grav/Common/Data/Blueprint.php invokes call_user_func_array() on an attacker-supplied Class::method callable string and its arguments with no allowlist or sanitization (CWE-94: Improper Control of Generation of Code).
  • Stage 1 — Payload planting (authenticated): An account holding the admin.pages or api.pages.write permission embeds a malicious callable directive inside a page’s YAML frontmatter via the Grav form plugin.
  • Stage 2 — Trigger (unauthenticated): Once the directive is stored, it executes as the web-server user automatically whenever any visitor — including completely unauthenticated internet users — loads the affected page over HTTP/HTTPS.
  • Attack vector: Fully network-accessible; no special network position or client interaction is required to trigger execution after the payload is planted.
  • Impact: Full remote code execution as the web-server process user, resulting in complete compromise of confidentiality, integrity, and availability of the affected host.
  • No public proof-of-concept was identified at time of publication (CVE published 2026-07-21); however, the underlying mechanism (unrestricted call_user_func_array via frontmatter) is well-documented within the PHP ecosystem and consistent with prior Grav exploit patterns.

Affected software

  • Grav CMS — all versions prior to 2.0.7

Severity

  • CVSS v3.1 base score: 9.8 (Critical)
  • CVSS v3.1 vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 base score: 9.3 (Critical)
  • CVSS v4.0 vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Grav CMS to version 2.0.7 or later. The 2.0.7 release includes a hardened Blueprint::dynamicData() implementation that refuses dangerous callable directives in dynamic field data.
  • If immediate patching is not possible:
    • Restrict or disable write access to page frontmatter for all accounts holding admin.pages or api.pages.write permissions until an upgrade can be applied.
    • Audit existing pages for unexpected callable directives in YAML frontmatter.
    • Apply network-level controls (WAF rules, IP allowlisting) on Grav admin endpoints to limit exposure of the page-editing interface.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge