grav up to 1.8.0-beta.27 Frontmatter Form /grav/user/accounts/ path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in grav up to 1.8.0-beta.27. The impacted element is an unknown function of the file /grav/user/accounts/ of the component Frontmatter Form. The manipulation leads to path traversal. This vulnerability is listed as CVE-2025-66300. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in grav up to 1.8.0-beta.27 and classified as critical. This issue affects some unknown functionality of the file /grav/user/accounts/ of the component Frontmatter Form. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, A low privilege user account with page editing privilege can read any server files using "Frontmatter" form. This includes Grav user account files (/grav/user/accounts/*.yaml), which store hashed user password, 2FA secret, and the password reset token. This can allow an adversary to compromise any registered account by resetting a password for a user to get access to the password reset token from the file or by cracking the hashed password. This vulnerability is fixed in 1.8.0-beta.27.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-66300 since 11/27/2025. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
Upgrading to version 1.8.0-beta.27 eliminates this vulnerability. Applying the patch ed640a13143c4177af013cf001969ed2c5e197ee is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 1.8.0-beta.0
- 1.8.0-beta.1
- 1.8.0-beta.2
- 1.8.0-beta.3
- 1.8.0-beta.4
- 1.8.0-beta.5
- 1.8.0-beta.6
- 1.8.0-beta.7
- 1.8.0-beta.8
- 1.8.0-beta.9
- 1.8.0-beta.10
- 1.8.0-beta.11
- 1.8.0-beta.12
- 1.8.0-beta.13
- 1.8.0-beta.14
- 1.8.0-beta.15
- 1.8.0-beta.16
- 1.8.0-beta.17
- 1.8.0-beta.18
- 1.8.0-beta.19
- 1.8.0-beta.20
- 1.8.0-beta.21
- 1.8.0-beta.22
- 1.8.0-beta.23
- 1.8.0-beta.24
- 1.8.0-beta.25
- 1.8.0-beta.26
- 1.8.0-beta.27
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: grav 1.8.0-beta.27
Patch: ed640a13143c4177af013cf001969ed2c5e197ee
Timeline
11/27/2025 CVE reserved12/01/2025 Advisory disclosed
12/01/2025 VulDB entry created
12/01/2025 VulDB entry last update
Sources
Advisory: GHSA-p4ww-mcp9-j6f2Status: Confirmed
CVE: CVE-2025-66300 (🔒)
GCVE (CVE): GCVE-0-2025-66300
GCVE (VulDB): GCVE-100-333923
Entry
Created: 12/01/2025 23:28Changes: 12/01/2025 23:28 (67)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.