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-66303: CWE-400: Uncontrolled Resource Consumption in getgrav grav

0
Medium
VulnerabilityCVE-2025-66303cvecve-2025-66303cwe-400
Published: Mon Dec 01 2025 (12/01/2025, 21:35:47 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 has been identified in Grav related to the handling of scheduled_at parameters. Specifically, the application fails to properly sanitize input for cron expressions. By manipulating the scheduled_at parameter with a malicious input, such as a single quote, the application admin panel becomes non-functional, causing significant disruptions to administrative operations. The only way to recover from this issue is to manually access the host server and modify the backup.yaml file to correct the corrupted cron expression. This vulnerability is fixed in 1.8.0-beta.27.

AI-Powered Analysis

AILast updated: 12/08/2025, 22:09:33 UTC

Technical Analysis

CVE-2025-66303 is a Denial of Service vulnerability classified under CWE-400 (Uncontrolled Resource Consumption) affecting the Grav CMS, a file-based web platform. The flaw exists in versions prior to 1.8.0-beta.27 and is related to the handling of the scheduled_at parameter, which accepts cron expressions for scheduling tasks. The application fails to properly sanitize this input, allowing an attacker with administrative privileges to inject malformed cron expressions, such as including a single quote character. This injection corrupts the backup.yaml configuration file, which is critical for the admin panel’s scheduled tasks. As a result, the admin panel becomes non-functional, effectively denying administrative access and control over the platform. The only remediation without patching is manual access to the host server to correct the corrupted cron expression in backup.yaml. The vulnerability requires authenticated access with high privileges but no user interaction beyond the attacker’s own actions. The CVSS 3.1 score is 4.9 (medium), reflecting the limited scope and required privileges but significant impact on availability. No known exploits are currently in the wild, and the issue was publicly disclosed on December 1, 2025. The fix is included starting with Grav version 1.8.0-beta.27.

Potential Impact

For European organizations using Grav CMS versions prior to 1.8.0-beta.27, this vulnerability poses a risk of administrative disruption. The inability to access or use the admin panel can delay or prevent critical content updates, security patching, and site management, potentially leading to extended downtime or degraded service quality. While the vulnerability does not expose sensitive data or allow unauthorized data modification, the loss of administrative availability can indirectly increase risk by delaying response to other threats. Organizations with strict uptime requirements or those managing multiple sites via Grav’s admin panel may experience operational and reputational impacts. Recovery requires manual server access, which may be challenging for organizations with limited technical staff or those relying on managed hosting. The vulnerability’s exploitation requires administrative credentials, so the risk is higher in environments with weak access controls or insider threats.

Mitigation Recommendations

European organizations should immediately upgrade Grav CMS to version 1.8.0-beta.27 or later to apply the official fix. Until upgrading, restrict administrative access to trusted personnel and enforce strong authentication mechanisms to reduce the risk of exploitation. Regularly audit scheduled tasks and the backup.yaml file for signs of corruption or unauthorized changes. Implement monitoring and alerting on admin panel availability and configuration file integrity to detect potential exploitation attempts early. Maintain secure backups of configuration files to enable rapid recovery without manual correction. Consider isolating the Grav admin panel behind VPNs or IP whitelisting to limit exposure. Educate administrators on the risks of malformed cron expressions and the importance of input validation. Finally, coordinate with hosting providers to ensure rapid manual intervention capability if needed.

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
3.1
State
PUBLISHED

Threat ID: 692e0bb43937fa579fdf7d4e

Added to database: 12/1/2025, 9:42:12 PM

Last enriched: 12/8/2025, 10:09:33 PM

Last updated: 1/16/2026, 1:34:57 AM

Views: 51

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