Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7317 medium CVSS 5.0

Vulnerability in getgrav/grav (CVE-2026-7317)

Summary

Vulnerability in getgrav/grav (CVE-2026-7317). Risk of unauthorized operations or information disclosure. Exploitable via FILECACHE_UNSERIALIZE_TRIGGERED. Mitigation: upgrade to 2.0.0-beta.2 or later.

Original description

The description as published by the source.

Insecure Deserialization in File Cache

  • Severity: High
  • CWE: CWE-502
  • Location: system/src/Grav/Framework/Cache/Adapter/FileCache.php
  • Sink: unserialize($value, ['allowed_classes' => true])

Affected version(s)

  • Affected: >= 1.7.44 and <= 1.7.49.5 (verified in current codebase and changelog-covered releases).
  • Fixed: No upstream fix identified in the reviewed branch at the time of analysis.
  • Notes: Earlier 1.7.x releases may also be affected, but were not fully back-traced in this review.

Notes

allowed_classes => true allows object instantiation and does not constrain classes.

PoC (Primitive Demonstration)

Preconditions

  • Local PHP runtime.
  • Goal is to validate the deserialization primitive used in cache retrieval.

Steps

php -r '
class CacheWakeup { public function __wakeup(){ file_put_contents("/tmp/grav_filecache_poc.txt", "wakeup"); } }

$payload = serialize(new CacheWakeup());
unserialize($payload, ["allowed_classes" => true]);

echo file_exists("/tmp/grav_filecache_poc.txt") ? "FILECACHE_UNSERIALIZE_TRIGGERED\n" : "FILECACHE_UNSERIALIZE_NOT_TRIGGERED\n";
'

Expected Result

  • Output contains: FILECACHE_UNSERIALIZE_TRIGGERED.

Interpretation

This reproduces the same unsafe primitive used by FileCache::doGet():
unserialize($value, ['allowed_classes' => true]).
If cache files are attacker-tampered, object magic methods may execute.

Exploit Preconditions

  • Cache file poison…

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-7317 has been found in getgrav/grav.
Attackers can target a specific entry point like FILECACHE_UNSERIALIZE_TRIGGERED over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/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-7317" on the vendor's site.

CVE-2026-7317 (getgrav/grav) — CWE-20 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: FILECACHE_UNSERIALIZE_TRIGGERED / c66dfeb5f / FilesystemAdapter
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

A vulnerability (CWE-20) exists in getgrav/grav. Attackers reach the vulnerable code path via FILECACHE_UNSERIALIZE_TRIGGERED.

📍 Affected scope

Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: FILECACHE_UNSERIALIZE_TRIGGERED / c66dfeb5f / FilesystemAdapter.

🔥 Severity

Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.

🔧 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

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.0-beta.2

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

  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.0-beta.2"}]}]
Packagist getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.2"}]}]

References

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