Skip to main content
VulnerabilityPublished

CVE-2025-66295: getgrav grav · Path Traversal

Affects getgrav gravSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in 1.8.0 : patch getgrav grav soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubgetgrav/gravpkg:github/getgrav/gravOther threatsAffected
  • =1.8.0-beta.27
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade Grav installations to version 1.8.0-beta.27 or later immediately to apply the official fix.
  2. Restrict user creation privileges strictly to trusted administrators and monitor account creation activities for suspicious patterns.
  3. Implement input validation and sanitization on usernames at the application or web server level to block path traversal sequences.
  4. Conduct regular audits of file system permissions to ensure that Grav cannot write outside intended directories.
  5. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attempts in user creation requests.
  6. Monitor logs for anomalous file write operations or unexpected account file locations.
  7. Educate administrators about the risks of path traversal and the importance of privilege management.
  8. Consider isolating Grav instances in containerized or sandboxed environments to limit potential damage from exploitation.

Description

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.

References

Community reviews

Loading reviews…