Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66295: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in getgrav grav

0
High
VulnerabilityCVE-2025-66295cvecve-2025-66295cwe-22
Published: Mon Dec 01 2025 (12/01/2025, 20:46:56 UTC)
Source: CVE Database V5
Vendor/Project: getgrav
Product: grav

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.

AI-Powered Analysis

AILast updated: 12/08/2025, 21:13:35 UTC

Technical Analysis

CVE-2025-66295 is a path traversal vulnerability classified under CWE-22 that affects Grav, a popular file-based web content management system. The flaw exists in versions prior to 1.8.0-beta.27 and is triggered when a user with the privilege to create new users inputs a username containing path traversal sequences (e.g., '..\Nijat' or '../Nijat') via the Admin UI. Instead of restricting file writes to the designated user/accounts/ directory, Grav improperly processes the pathname and writes the YAML account file outside this directory. These YAML files contain sensitive account information such as email addresses, full names, two-factor authentication secrets, and hashed passwords. Exploiting this vulnerability could allow an attacker with user creation privileges to overwrite or create arbitrary files on the server, potentially leading to privilege escalation, unauthorized access, or denial of service. The vulnerability is remotely exploitable over the network without user interaction but requires authenticated access with user creation rights. The CVSS v3.1 base score is 8.8, reflecting high impact on confidentiality, integrity, and availability. Although no public exploits are currently known, the vulnerability poses a significant risk to Grav installations that have not been updated to version 1.8.0-beta.27 or later.

Potential Impact

For European organizations, this vulnerability could lead to severe consequences including unauthorized access to user accounts, leakage of sensitive user data, and potential full compromise of Grav-based web platforms. Since Grav is used to manage website content and user accounts, exploitation could allow attackers to manipulate website content, create backdoors, or disrupt services. This can damage organizational reputation, lead to data breaches under GDPR regulations, and cause operational downtime. Organizations that rely on Grav for critical public-facing websites or internal portals are particularly at risk. The requirement for authenticated user creation privileges limits exposure somewhat, but insider threats or compromised accounts could still exploit this flaw. The high CVSS score indicates that the vulnerability can have a broad and damaging impact on confidentiality, integrity, and availability of affected systems.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-26T23:11:46.393Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692e0147821c4e4a8f8d8923

Added to database: 12/1/2025, 8:57:43 PM

Last enriched: 12/8/2025, 9:13:35 PM

Last updated: 1/16/2026, 5:18:57 AM

Views: 53

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats