getgrav/grav · Grav vulnerable to Path traversal / arbitrary YAML write via user creation leading to Account Takeover / System
Affects getgrav/gravSource GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 1.8.0-beta.27 soon.
Data as of 21 Nov 2026, 03:47 UTC
- Patch
- Available – fixed in 1.8.0-beta.27
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade getgrav/grav to 1.8.0-beta.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistgetgrav/grav | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Grav version 1.8.0-beta.27 that fixes this vulnerability. Users should upgrade to this version or later to remediate the issue. No additional mitigation steps are required if the patch is applied.
Description
A path traversal vulnerability in Grav prior to version 1.8.0-beta.27 allows users with user creation privileges to write arbitrary YAML files outside the intended directory via crafted usernames. This can lead to overwriting critical configuration files and account takeover by modifying other users' credentials.