Unsafe Callable Execution in Grav Blueprint Data Handling

Grav 2.0.4 (fixed in 2.0.7) contains a remote code execution vulnerability in Blueprint::dynamicData() (system/src/Grav/Common/Data/Blueprint.php), which passes a Class::method callable string and its arguments directly to call_user_func_array() without any allowlist. Because the form plugin routes page frontmatter through this path, an authenticated account with the admin.pages (or api.pages.write) permission can plant a malicious callable directive in a page. The command then executes as the web-server user whenever anyone — including an unauthenticated visitor — accesses the page.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Grav 2.0.4 and earlier versions contain a critical remote code execution vulnerability in the Blueprint::dynamicData() function that fails to validate callable directives before passing them to call_user_func_array(). This vulnerability affects authenticated users with admin.pages or api.pages.write permissions, allowing them to inject malicious PHP callable strings through page frontmatter. Since the form plugin routes frontmatter through this vulnerable code path, attackers with legitimate admin credentials—or those who have compromised such accounts—can execute arbitrary code with the privileges of the web server process. This represents a significant risk for multi-user Grav installations and organizations where administrative access may be delegated to untrusted users.

Casky's 322 matched security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability by mapping indicators across MITRE ATT&CK's Initial Access (TA0001) and Persistence (TA0043) techniques. Practitioners using Casky would observe detections for CWE-94 (Improper Control of Generation of Code) through behavioral analysis of unsafe reflection and dynamic callable execution. The platform identifies suspicious patterns such as user-controlled input flowing into call_user_func_array(), frontmatter directives containing class::method syntax without validation, and code execution attempts originating from page administration endpoints. By correlating these indicators with the form plugin's data processing pipeline, Casky helps security teams pinpoint the exact code paths where malicious callables could be injected and the conditions required to exploit them, enabling both rapid patching decisions and forensic investigation of compromised instances.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-65008.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-65008

Casky has 322 skills that investigate the attack patterns behind CVE-2026-65008. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn