CVE-2025-66300
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 in Grav, a file-based web platform, allows a low privilege user with page editing rights to read any server files using the 'Frontmatter' form. This includes sensitive Grav user account files that contain hashed passwords, 2FA secrets, and password reset tokens. An attacker could exploit this to compromise user accounts by resetting passwords or cracking hashed passwords. The issue was fixed in version 1.8.0-beta.27.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to sensitive user account information, including hashed passwords and 2FA secrets. This can allow an attacker to compromise any registered user account by resetting passwords or cracking password hashes, potentially leading to account takeover and unauthorized access to the web platform.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Grav to version 1.8.0-beta.27 or later, as this version contains the fix for the vulnerability allowing low privilege users with page editing privileges to read any server files. Until the upgrade is applied, restrict page editing privileges to trusted users only to minimize risk.