grav up to 1.8.0-beta.27 POST Request /admin/pages/ page_name improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in grav up to 1.8.0-beta.27. This issue affects some unknown processing of the file /admin/pages/ of the component POST Request Handler. Performing a manipulation of the argument page_name results in improper authorization. This vulnerability is cataloged as CVE-2025-66301. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in grav up to 1.8.0-beta.27. This affects some unknown functionality of the file /admin/pages/ of the component POST Request Handler. The manipulation of the argument page_name with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, due to improper authorization checks when modifying critical fields on a POST request to /admin/pages/{page_name}, an editor with only permissions to change basic content on the form is now able to change the functioning of the form through modifying the content of the data[_json][header][form] which is the YAML frontmatter which includes the process section which dictates what happens after a user submits the form which include some important actions that could lead to further vulnerabilities. This vulnerability is fixed in 1.8.0-beta.27.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-66301 since 11/27/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 1.8.0-beta.27 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.8
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.6
NVD Vector: 🔒
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: Improper authorizationCWE: CWE-285 / CWE-266
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
Timeline
11/27/2025 CVE reserved12/01/2025 Advisory disclosed
12/01/2025 VulDB entry created
12/03/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-66301 (🔒)
GCVE (CVE): GCVE-0-2025-66301
GCVE (VulDB): GCVE-100-333909
Entry
Created: 12/01/2025 23:24Updated: 12/03/2025 17:20
Changes: 12/01/2025 23:24 (68), 12/03/2025 17:20 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.