grav up to 1.8.0-beta.27 /admin/config/system uncaught exception
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in grav up to 1.8.0-beta.27. This affects an unknown part of the file /admin/config/system. The manipulation leads to uncaught exception. This vulnerability is traded as CVE-2025-66305. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in grav up to 1.8.0-beta.27. This issue affects an unknown functionality of the file /admin/config/system. The manipulation with an unknown input leads to a uncaught exception vulnerability. Using CWE to declare the problem leads to CWE-248. An exception is thrown from a function, but it is not caught. Impacted is availability. The summary by CVE is:
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, a Denial of Service (DoS) vulnerability was identified in the "Languages" submenu of the Grav admin configuration panel (/admin/config/system). Specifically, the Supported parameter fails to properly validate user input. If a malformed value is inserted—such as a single forward slash (/) or an XSS test string—it causes a fatal regular expression parsing error on the server. This leads to application-wide failure due to the use of the preg_match() function with an improperly constructed regular expression, resulting in an error. Once triggered, the site becomes completely unavailable to all users. This vulnerability is fixed in 1.8.0-beta.27.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-66305 since 11/27/2025. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-200105). Several companies clearly confirm that VulDB is the primary source for best 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: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.9
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: Uncaught exceptionCWE: CWE-248
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/04/2025 VulDB entry last update
Sources
Advisory: GHSA-m8vh-v6r6-w7p6Status: Confirmed
CVE: CVE-2025-66305 (🔒)
GCVE (CVE): GCVE-0-2025-66305
GCVE (VulDB): GCVE-100-333929
EUVD: 🔒
Entry
Created: 12/01/2025 23:30Updated: 12/04/2025 07:50
Changes: 12/01/2025 23:30 (68), 12/02/2025 22:05 (1), 12/04/2025 07:50 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.