Code Injection in getgrav/grav (CVE-2026-69088)
Summary
Code injection in getgrav/grav (CVE-2026-69088). Confidential information can be exposed externally. Exploitable via POST /admin/pages/. Mitigation: upgrade to 2.0.11 or later.
Original description
The description as published by the source.
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.pages_twig) 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.
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-69088 has been found in getgrav/grav.
Attackers can target a specific entry point like POST /admin/pages/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade getgrav/grav to 2.0.11 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-69088" on the vendor's site.
CVE-2026-69088 (getgrav/grav) — CWE-94 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /admin/pages/ / admin.pages / Blueprint.php / admin.pages_twig
Patched: 2.0.11 — 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 getgrav/grav. Attackers reach the vulnerable code path via POST /admin/pages/.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: POST /admin/pages/ / admin.pages / Blueprint.php / admin.pages_twig.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 2.0.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /admin/pages/ requests with malformed payloads or SQL meta-characters. Run grep -r 'getgrav/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 'getgrav/grav' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
getgrav/gravを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /admin/pages/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /admin/pages/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade getgrav/grav to 2.0.11ステージング環境で 2.0.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /admin/pages/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- web github.com
- web github.com