Categories
CVE-2026-64850

Code Injection in getgrav/grav (CVE-2026-64850)

Summary

Code injection in getgrav/grav (CVE-2026-64850). Risk of unauthorized operations or information disclosure. Exploitable via admin.pages. Mitigation: upgrade to 2.0.7 or later.

Original description

The description as published by the source.

Grav is a file-based Web platform. Prior to 2.0.7, Grav Blueprint::dynamicData() in system/src/Grav/Common/Data/Blueprint.php sends an editor-controlled Class::method provider and arguments to call_user_func_array() without rejecting dangerous callback parameters. An account with admin.pages or api.pages.write can use Grav\Common\Utils::arrayFilterRecursive() as a trampoline with system as the callback, place a command in page frontmatter, and execute that command as the web server user when the page is viewed. This issue is fixed in version 2.0.7.

Source: NIST National Vulnerability Database 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-64850 has been found in getgrav/grav.
Attackers can target a specific entry point like admin.pages over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade getgrav/grav to 2.0.7 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-64850" on the vendor's site.

CVE-2026-64850 (getgrav/grav) — CWE-94
Attack surface: admin.pages / api.pages.write / system / window.GravAdmin.config.admin_nonce
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.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in getgrav/grav. Attackers reach the vulnerable code path via admin.pages.

📍 Affected scope

Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: admin.pages / api.pages.write / system / window.GravAdmin.config.admin_nonce.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.0.7.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'getgrav/grav' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で getgrav/grav を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade getgrav/grav to 2.0.7

    ステージング環境で 2.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.7"}]}]
Packagist getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details