← Back
CVE-2026-42607
critical
CVSS 9.1
Code Injection in getgrav/grav (CVE-2026-42607)
Summary
code injection in getgrav/grav (CVE-2026-42607). Successful exploitation can lead to full system takeover. Exploitable via ``directInstall``. Mitigation: upgrade to `2.0.0-beta.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42607** has been found in getgrav/grav.
Attackers can target a specific entry point like ``directInstall`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: upgrade getgrav/grav to **2.0.0-beta.2** or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-42607" on the vendor's site.
CVE-2026-42607 (getgrav/grav) — CWE-94 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `directInstall`
Patched: `2.0.0-beta.2` — 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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in getgrav/grav. Attackers reach the vulnerable code path via ``directInstall`` without authentication.
📍 Affected scope
getgrav/grav — . Attack surface: `directInstall`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.0.0-beta.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'getgrav/grav' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade getgrav/grav to 2.0.0-beta.2ステージング環境で 2.0.0-beta.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.2"}]}]
Packagist
getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42607
- package https://github.com/getgrav/grav
- web https://github.com/getgrav/grav/commit/5a12f9be8314682c8713e569e330f11805d0a663
- web https://github.com/getgrav/grav/security/advisories/GHSA-w48r-jppp-rcfw
- web https://github.com/advisories/GHSA-w48r-jppp-rcfw