Low

Grav has Insecure Deserialization in File Cache

  • Disclosed: 05.05.2026
  • Updated: 11.10.2026 10:22

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

bash
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 poisoning/tampering capability.

Recommendation

  • Avoid object deserialization in cache payloads.
  • Use non-object formats and integrity protection for cache files.

Maintainer note — fix applied (2026-04-24)

Fixed in Grav core on the 2.0 branch: commit c66dfeb5f — will ship in 2.0.0-beta.2.

What changed: Framework\Cache\Adapter\FileCache now HMAC-signs every cache payload with Security::getNonceKey() on write, and verifies the HMAC on read. Tampered, forged, or pre-upgrade files are treated as cache misses and unlinked instead of being unserialized. The on-disk format is now versioned:

v2
<expires>
<key>
<hmac-hex>
<serialized>

Existing caches rebuild transparently on first read. Note that Framework\Cache\Adapter\FileCache isn't wired into Grav's main cache path — Symfony's FilesystemAdapter is — but the class is reachable by plugin and downstream consumers, so the hardening applies defensively.

Files:

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package getgrav/grav < 2.0.0-beta.2 2.0.0-beta.2

References

CVSS score 5/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Weakness (CWE)
CWE-20, CWE-502
Platform
Composer
Package
getgrav/grav
Disclosed
05.05.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-gwfr-jfjf-92vv - CC BY 4.0

Vulnerability history: getgrav/grav

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (99) in the archive
Total entries
99
First → latest
11.2019 09.2026
Without a fix
6
Exploited in attacks
0

Severity breakdown

  • Critical 7
  • High 47
  • Medium 41
  • Low 4

Disclosures per year

  1. 2019: 1
  2. 2020: 1
  3. 2021: 4
  4. 2022: 10
  5. 2023: 5
  6. 2024: 8
  7. 2025: 23
  8. 2026: 47
Severity:
  1. High · 8.8 CVE-2026-72819 < 2.0.13 2.0.13
  2. High CVE-2026-53653 >= 2.0.0-beta.1, < 2.0.0-rc.8, < 1.7.53 2.0.0-rc.8, 1.7.53
  3. High · 8.9 CVE-2026-42611 < 2.0.0-beta.2 2.0.0-beta.2
  4. Grav has Insecure Deserialization in File Cache this entry
    Low · 5.0 CVE-2026-7317 < 2.0.0-beta.2 2.0.0-beta.2
  5. High · 8.5 CVE-2026-42612 < 2.0.0-beta.2 2.0.0-beta.2
  6. Critical · 9.4 CVE-2026-42613 < 2.0.0-beta.2 2.0.0-beta.2
  7. Critical · 9.1 CVE-2025-66844 <= 1.7.49.5 no fix
  8. High CVE-2025-66298 < 1.8.0-beta.27 1.8.0-beta.27
  9. High CVE-2025-66294 < 1.8.0-beta.27 1.8.0-beta.27
  10. High · 8.5 CVE-2025-66300 < 1.8.0-beta.27 1.8.0-beta.27
  11. High · 8.8 CVE-2025-66299 < 1.8.0-beta.27 1.8.0-beta.27
  12. High · 8.5 CVE-2024-34082 < 1.7.46 1.7.46
  13. High · 8.8 CVE-2024-28119 < 1.7.45 1.7.45
  14. High · 8.8 CVE-2024-28118 < 1.7.45 1.7.45
  15. High · 8.8 CVE-2024-28117 < 1.7.45 1.7.45
  16. High · 8.8 CVE-2024-27921 < 1.7.45 1.7.45
  17. High · 8.8 CVE-2024-27923 < 1.7.43 1.7.43
  18. High · 7.2 CVE-2023-37897 < 1.7.42.2 1.7.42.2
  19. High · 7.2 CVE-2023-34448 < 1.7.42 1.7.42
  20. High · 7.2 CVE-2023-34252 < 1.7.42 1.7.42
  21. Critical · 9.1 CVE-2023-34251 < 1.7.42 1.7.42
  22. High · 7.2 CVE-2022-2073 < 1.7.34 1.7.34
  23. High · 8.1 CVE-2020-29555 >= 1.7.0-beta.1, <= 1.7.0-rc.17, < 1.6.30 1.6.30
  24. High · 8.8 CVE-2020-29553 >= 1.7.0-beta.1, <= 1.7.0-rc.17, < 1.6.30 1.6.30
  25. High · 7.1 CVE-2022-0970 < 1.7.31 1.7.31
  26. High · 8.8 CVE-2021-3924 <= 1.7.24 no fix
  27. High · 8.4 CVE-2021-29440 < 1.7.11 1.7.11

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.