CVE-2025-66302
BaseFortify
Publication date: 2025-12-01
Last updated on: 2025-12-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| getgrav | grav | to 1.8.0 (exc) |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
| getgrav | grav | 1.8.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a path traversal issue in Grav CMS prior to version 1.8.0-beta.27. It allows authenticated users with administrative privileges to read arbitrary files on the server by exploiting insufficient input sanitization in the backup tool. Specifically, user-supplied paths are not properly restricted, enabling access to files outside the intended webroot directory.
How can this vulnerability impact me? :
If exploited, this vulnerability can allow an attacker with administrative access to read sensitive files on the server that should not be accessible, potentially exposing confidential information. The impact depends on the privileges of the user account running the application, but it can lead to significant data exposure.
What immediate steps should I take to mitigate this vulnerability?
Update Grav CMS to version 1.8.0-beta.27 or later, as this version contains the fix for the path traversal vulnerability. Additionally, restrict administrative access to trusted users only and monitor for any unusual file access patterns.