Path Traversal in Grav (CVE-2025-66295)
Summary
Path traversal in Grav (CVE-2025-66295). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.8.0-beta.27 or later.
Original description
The description as published by the source.
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, when a user with privilege of user creation creates a new user through the Admin UI and supplies a username containing path traversal sequences (for example ..\Nijat or ../Nijat), Grav writes the account YAML file to an unintended path outside user/accounts/. The written YAML can contain account fields such as email, fullname, twofa_secret, and hashed_password. This vulnerability is fixed in 1.8.0-beta.27.
Source: NIST National Vulnerability Database NVD
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-2025-66295 has been found in Grav.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Grav to 1.8.0-beta.27 or later.
If unsure, ask your IT team or search "Grav CVE-2025-66295" on the vendor's site.
CVE-2025-66295 (Grav) — CWE-22 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.8.0-beta.27 — 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.
Path traversal (CWE-22) exists in Grav.
Check the vendor advisory for the affected versions of Grav.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.8.0-beta.27.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '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 'Grav' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Gravを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Grav to 1.8.0-beta.27ステージング環境で 1.8.0-beta.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。