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-66306: CWE-639: Authorization Bypass Through User-Controlled Key in getgrav grav

0
Medium
VulnerabilityCVE-2025-66306cvecve-2025-66306cwe-639
Published: Mon Dec 01 2025 (12/01/2025, 21:46:00 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, there is an IDOR (Insecure Direct Object Reference) vulnerability in the Grav CMS Admin Panel which allows low-privilege users to access sensitive information from other accounts. Although direct account takeover is not possible, admin email addresses and other metadata can be exposed, increasing the risk of phishing, credential stuffing, and social engineering. This vulnerability is fixed in 1.8.0-beta.27.

AI-Powered Analysis

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

Technical Analysis

CVE-2025-66306 is classified under CWE-639 (Authorization Bypass Through User-Controlled Key) and affects the Grav CMS, a popular file-based web platform used for content management. The vulnerability resides in the Admin Panel component of Grav versions before 1.8.0-beta.27. It is an IDOR flaw that allows authenticated users with low privileges to manipulate object references or keys to access sensitive information belonging to other users. Specifically, attackers can retrieve admin email addresses and other metadata that should be restricted. Although the vulnerability does not permit direct account takeover or modification of data, the leakage of sensitive metadata can facilitate secondary attacks such as phishing campaigns, credential stuffing, or social engineering. The vulnerability requires the attacker to have some level of authenticated access (low privilege) but does not require user interaction or elevated privileges. The CVSS 3.1 score is 4.3 (medium), reflecting the limited impact on confidentiality and no impact on integrity or availability. No public exploits have been reported, and the issue is resolved in Grav 1.8.0-beta.27. Organizations using Grav CMS should verify their version and apply updates accordingly to mitigate risk.

Potential Impact

For European organizations using Grav CMS, this vulnerability poses a moderate risk primarily through the exposure of sensitive administrative metadata. The leakage of admin email addresses can lead to targeted phishing attacks, which are a common vector for initial compromise in European enterprises. Credential stuffing attacks could also be facilitated if attackers correlate exposed emails with leaked password databases. Although the vulnerability does not allow direct account takeover or system compromise, the indirect risks can lead to significant security incidents, including unauthorized access and data breaches. Organizations in sectors with high regulatory requirements for data protection (e.g., finance, healthcare, government) may face compliance risks if such metadata exposure leads to further compromise. The impact is heightened in environments where Grav CMS is used to manage critical or sensitive web content. Since exploitation requires low-privilege authenticated access, insider threats or compromised low-level accounts increase the risk profile.

Mitigation Recommendations

1. Upgrade Grav CMS installations to version 1.8.0-beta.27 or later immediately to apply the patch that fixes this vulnerability. 2. Review and restrict user privileges in the Grav Admin Panel to the minimum necessary, limiting access to trusted users only. 3. Implement strong authentication mechanisms, such as multi-factor authentication (MFA), to reduce the risk of low-privilege account compromise. 4. Monitor access logs for unusual or unauthorized attempts to access user metadata or admin panel resources. 5. Educate administrative users about phishing and social engineering risks, especially given the potential exposure of their email addresses. 6. Consider additional application-layer access controls or web application firewalls (WAFs) that can detect and block suspicious IDOR exploitation attempts. 7. Conduct regular security audits and vulnerability scans focusing on CMS components to detect outdated versions or misconfigurations.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 692e0ef03937fa579fe46181

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

Last enriched: 12/1/2025, 10:10:10 PM

Last updated: 12/1/2025, 11:15:12 PM

Views: 3

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats