Code Injection in getgrav/grav (CVE-2026-72819)
Summary
Code injection in getgrav/grav (CVE-2026-72819). Successful exploitation can lead to full system takeover. Exploitable via PATCH /api/v1/config/plugins/flex-objects. Mitigation: upgrade to 2.0.13 or later.
Original description
The description as published by the source.
Grav CMS before 2.0.13 contains a remote code execution vulnerability in the Flex Objects plugin settings validation that allows authenticated users to execute arbitrary code by uploading a ZIP file containing PHP code. Attackers can bypass routine name validation by using array notation instead of string notation, call the unZip routine with a malicious archive, and write PHP files to the web root for execution.
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-72819 has been found in getgrav/grav.
Attackers can target a specific entry point like PATCH /api/v1/config/plugins/flex-objects over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade getgrav/grav to 2.0.13 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-72819" on the vendor's site.
CVE-2026-72819 (getgrav/grav) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/v1/config/plugins/flex-objects / POST /api/v1/flex-objects/flex-objects
Patched: 2.0.13 — 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 PATCH /api/v1/config/plugins/flex-objects.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: PATCH /api/v1/config/plugins/flex-objects / POST /api/v1/flex-objects/flex-objects.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.0.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /api/v1/config/plugins/flex-objects 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 'PATCH /api/v1/config/plugins/flex-objects' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/v1/config/plugins/flex-objectsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade getgrav/grav to 2.0.13ステージング環境で 2.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PATCH /api/v1/config/plugins/flex-objects 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