Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66305: CWE-248: Uncaught Exception in getgrav grav

0
Medium
VulnerabilityCVE-2025-66305cvecve-2025-66305cwe-248
Published: Mon Dec 01 2025 (12/01/2025, 21:43:29 UTC)
Source: CVE Database V5
Vendor/Project: getgrav
Product: grav

Description

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.

AI-Powered Analysis

AILast updated: 12/08/2025, 22:12:01 UTC

Technical Analysis

CVE-2025-66305 is a vulnerability in the Grav CMS platform, specifically in versions before 1.8.0-beta.27. Grav is a file-based web platform used for building websites without a database backend. The vulnerability resides in the 'Languages' submenu of the admin configuration panel (/admin/config/system), where the 'Supported' parameter accepts user input that is not properly validated. When a malformed input—such as a single forward slash (/) or an XSS test string—is submitted, it causes the preg_match() function to process an improperly constructed regular expression. This results in a fatal regular expression parsing error, which is an uncaught exception leading to a denial of service. The entire Grav application becomes unavailable, causing a site-wide outage. The CVSS 4.0 score is 6.9 (medium severity), reflecting network attack vector, low attack complexity, no privileges required for the attacker, no user interaction, but requiring high privileges (administrative) on the system. No known exploits are currently in the wild, and the issue is resolved in Grav version 1.8.0-beta.27. The root cause is categorized under CWE-248 (Uncaught Exception).

Potential Impact

For European organizations, this vulnerability can cause complete service outages of websites or web applications running on vulnerable Grav versions. Since Grav is often used for content management and small to medium business websites, an outage can disrupt business operations, customer access, and damage reputation. The DoS nature means attackers can render sites unavailable without needing to steal data or escalate privileges beyond admin access. Organizations relying on Grav for critical web presence or internal portals may experience significant operational impact. Additionally, if attackers gain administrative access through other means, they could exploit this vulnerability to cause denial of service, amplifying the damage. The lack of user interaction and network attack vector means the vulnerability can be exploited remotely once admin access is compromised, increasing risk.

Mitigation Recommendations

1. Upgrade all Grav installations to version 1.8.0-beta.27 or later immediately to apply the patch that fixes this vulnerability. 2. Restrict access to the Grav admin panel (/admin) using network-level controls such as IP whitelisting, VPNs, or firewall rules to limit exposure to trusted administrators only. 3. Implement strong authentication and authorization controls to prevent unauthorized administrative access, including multi-factor authentication (MFA). 4. Monitor web server and application logs for unusual requests targeting the 'Languages' submenu or malformed input patterns that could indicate exploitation attempts. 5. Conduct regular security audits and vulnerability scans on Grav installations to detect outdated versions or misconfigurations. 6. Consider implementing Web Application Firewalls (WAF) with custom rules to detect and block suspicious regular expression patterns or malformed inputs targeting the affected parameter. 7. Educate administrators on secure configuration practices and the importance of timely patching.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-26T23:11:46.395Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 692e0ef03937fa579fe4618a

Added to database: 12/1/2025, 9:56:00 PM

Last enriched: 12/8/2025, 10:12:01 PM

Last updated: 1/16/2026, 3:04:36 AM

Views: 60

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats