GHSA-gpmf-q5jh-hjx4 — getgrav/grav
HIGHGHSA-gpmf-q5jh-hjx4 is a high-severity (CVSS 8.1) Path Traversal vulnerability in getgrav/grav. 1 public exploit reference exists, so weaponization risk is real. A fix is available for getgrav/grav — see the affected versions and patch details below.
Grav CMS Arbitrary File Deletion
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-gpmf-q5jh-hjx4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
getgrav/grav🐘getgrav/gravReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The BackupDelete functionality in Grav CMS through 1.7.0-rc.17 allows an authenticated attacker to delete arbitrary files on the underlying server by exploiting a path-traversal technique. (This vulnerability can also be exploited by an unauthenticated attacker due to a lack of CSRF protection.)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | getgrav/grav | ≥ 1.7.0-beta.1 | No fix |
| 🐘Packagist | getgrav/grav | all versions | 1.6.30composer require getgrav/grav:^1.6.30 |
Affected Products
grav cmsgetgravResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getgrav/grav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of getgrav/grav has shipped for GHSA-gpmf-q5jh-hjx4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-gpmf-q5jh-hjx4 in your dependencies?
Find it across Packagist, including transitive dependencies.