Code Injection in Grav (CVE-2026-65008)
Summary
Code injection in Grav (CVE-2026-65008). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.0.7 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65008 has been found in Grav.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade Grav to 2.0.7 or later.
If unsure, ask your IT team or search "Grav CVE-2026-65008" on the vendor's site.
CVE-2026-65008 (Grav) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in Grav.
Check the vendor advisory for the affected versions of Grav.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2.0.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Grav' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Grav' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Gravを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Grav to 2.0.7ステージング環境で 2.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- web github.com