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-65186: n/a

0
High
VulnerabilityCVE-2025-65186cvecve-2025-65186
Published: Tue Dec 02 2025 (12/02/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2025-65186 is a stored Cross Site Scripting (XSS) vulnerability in Grav CMS version 1. 7. 49. Authenticated users can inject malicious <script> tags via the Markdown page editor, which are not properly sanitized. When these pages are viewed in the admin interface, the malicious scripts execute, potentially compromising admin sessions and data. This vulnerability requires authentication but no additional user interaction beyond viewing the infected page in the admin panel. Although no known exploits are currently reported in the wild, the flaw poses a significant risk to the confidentiality and integrity of Grav CMS installations. European organizations using Grav CMS for content management are at risk, especially those with multiple administrators. Mitigation involves applying patches once available, restricting editor permissions, and implementing additional input sanitization controls. Countries with higher Grav CMS adoption and active web development communities, such as Germany, the UK, France, and the Netherlands, are more likely to be affected.

AI-Powered Analysis

AILast updated: 12/02/2025, 16:21:28 UTC

Technical Analysis

CVE-2025-65186 identifies a stored Cross Site Scripting (XSS) vulnerability in Grav CMS version 1.7.49, a popular flat-file content management system. The vulnerability arises from improper sanitization of <script> tags within the Markdown editor used by authenticated users to edit page content. Specifically, the editor fails to neutralize or remove malicious JavaScript code embedded in the page content. When an administrator or any user with access to the admin interface views the infected page, the stored XSS payload executes in their browser context. This can lead to session hijacking, privilege escalation, or unauthorized actions within the CMS. The attack vector requires the attacker to have authenticated access to the CMS to inject the payload, but no further user interaction is needed beyond viewing the compromised page. The vulnerability does not currently have a CVSS score and no public exploits have been reported. However, the flaw is significant because it targets the administrative interface, which typically has elevated privileges and access to sensitive content and configurations. The lack of proper input validation and output encoding in the Markdown editor is the root cause. This vulnerability could be leveraged by malicious insiders or attackers who have gained low-level access to the CMS to escalate their privileges or compromise the system integrity.

Potential Impact

For European organizations using Grav CMS, this vulnerability could lead to unauthorized administrative actions, data theft, or defacement of web content. Since the XSS is stored and executes in the admin interface, attackers could hijack admin sessions, inject further malicious code, or manipulate site content and configurations. This threatens the confidentiality, integrity, and availability of the CMS-managed websites. Organizations with multiple administrators or editors are at higher risk due to increased exposure. The impact is particularly critical for sectors relying on Grav CMS for public-facing or internal portals, including government, education, and media entities in Europe. Compromise could result in reputational damage, regulatory non-compliance (e.g., GDPR breaches if personal data is exposed), and operational disruptions. The requirement for authentication limits the attack surface but does not eliminate risk, especially if credential theft or insider threats are present.

Mitigation Recommendations

1. Apply official patches or updates from Grav CMS as soon as they become available to address this vulnerability. 2. Until patches are released, restrict page editing permissions to only highly trusted users and minimize the number of users with admin or editor roles. 3. Implement additional input validation and sanitization controls at the web application firewall (WAF) or reverse proxy level to detect and block malicious script tags in Markdown content. 4. Conduct regular audits of page content for suspicious scripts or injected code, especially in pages edited recently. 5. Enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 6. Educate administrators and editors about the risks of XSS and safe content editing practices. 7. Monitor logs and user activity for unusual behavior indicative of exploitation attempts. 8. Consider isolating the admin interface behind VPN or IP allowlists to limit access to trusted networks.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-18T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 692f11fa0eb63243a5f7cdc5

Added to database: 12/2/2025, 4:21:14 PM

Last enriched: 12/2/2025, 4:21:28 PM

Last updated: 12/2/2025, 4:21:42 PM

Views: 1

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