CVE-2026-69088: Grav CMS 2.0.7 through 2.0.10 Arbitrary Method Invocation via Blueprint
Grav CMS versions 2.0.7 through 2.0.10 fail to validate fully-qualified static method calls (Class::method) in blueprint dynamic-field directives because Blueprint::isSafeDynamicCall() only applies its dangerous-callable denylist to strings that do not contain '::'. An account with only page-editing rights (admin.pages, not super-admin or admin.pagestwig) can plant a directive in a page's form-field frontmatter that invokes an arbitrary public static PHP method with attacker-controlled arguments. Using built-in gadget methods this allows reading of any server-readable file (disclosed to anonymous visitors of the crafted page) and arbitrary creation/copying of files and directories under the web-server account. Fixed in 2.0.11.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Grav CMSto a version that resolves this vulnerability.Fixed in 2.0.11
Event History
Frequently Asked Questions
What is the severity of CVE-2026-69088?
The severity of CVE-2026-69088 is high with a score of 8.1.
How do I fix CVE-2026-69088?
To fix CVE-2026-69088, upgrade Grav CMS to version 2.0.11 or later.
What are the potential consequences of exploiting CVE-2026-69088?
Exploiting CVE-2026-69088 could lead to arbitrary code execution through arbitrary method invocation.
Which versions of Grav CMS are affected by CVE-2026-69088?
Grav CMS versions 2.0.7 through 2.0.10 are affected by CVE-2026-69088.
What type of vulnerability is CVE-2026-69088 classified as?
CVE-2026-69088 is classified as a Code Injection vulnerability.