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-66468: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in aimeos ai-cms-grapesjs

0
High
VulnerabilityCVE-2025-66468cvecve-2025-66468cwe-79
Published: Tue Dec 02 2025 (12/02/2025, 18:40:44 UTC)
Source: CVE Database V5
Vendor/Project: aimeos
Product: ai-cms-grapesjs

Description

The Aimeos GrapesJS CMS extension provides page editor for creating content pages based on extensible components. Prior to 2021.10.8, 2022.10.8, 2023.10.8, 2024.10.8, and 2025.10.8, Javascript code can be injected by malicious editors for a stored XSS attack if the standard Content Security Policy is disabled. This vulnerability is fixed in 2021.10.8, 2022.10.8, 2023.10.8, 2024.10.8, and 2025.10.8.

AI-Powered Analysis

AILast updated: 12/02/2025, 19:21:13 UTC

Technical Analysis

CVE-2025-66468 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79 affecting the Aimeos ai-cms-grapesjs extension, a CMS page editor used for creating content pages with extensible components. The vulnerability exists in versions prior to 2021.10.8, 2022.10.8, 2023.10.8, 2024.10.8, and 2025.10.8, across multiple release lines. The root cause is improper neutralization of input during web page generation, allowing malicious editors to inject arbitrary JavaScript code into stored content. This injected script executes in the context of users viewing the compromised pages, potentially leading to session hijacking, credential theft, or further exploitation of the web application. The attack requires that the standard Content Security Policy (CSP) be disabled, which otherwise would mitigate script injection. Exploitation requires authenticated editor privileges and user interaction to trigger the malicious payload. The vulnerability has a CVSS v3.1 score of 7.7, reflecting high impact on confidentiality, integrity, and availability, with attack vector being network-based but requiring high privileges and user interaction. Although no known exploits are reported in the wild, the vulnerability poses a significant risk to organizations using affected versions of the Aimeos ai-cms-grapesjs CMS extension, especially those that have disabled or weakened CSP configurations. The issue is fixed in the specified 10.x.x patch releases for each affected year/version line.

Potential Impact

For European organizations, this vulnerability can lead to severe consequences including unauthorized access to sensitive data, session hijacking, defacement of web content, and potential pivoting to internal networks. Since the vulnerability allows execution of arbitrary JavaScript in the context of the affected web application, attackers can steal authentication tokens, manipulate user sessions, and perform actions on behalf of legitimate users. This is particularly critical for e-commerce platforms and content management systems that handle personal data and payment information, increasing risks of data breaches and regulatory non-compliance under GDPR. The requirement for authenticated editor privileges limits exposure but insider threats or compromised editor accounts can be exploited. Disabling or misconfiguring CSP, which is a common practice in some deployments, significantly increases risk. The impact extends to brand reputation damage and potential financial losses due to fraud or remediation costs. Given the widespread use of Aimeos in European e-commerce and CMS solutions, the threat is material and demands urgent remediation.

Mitigation Recommendations

1. Immediately upgrade affected Aimeos ai-cms-grapesjs installations to the fixed versions: 2021.10.8, 2022.10.8, 2023.10.8, 2024.10.8, or 2025.10.8 as applicable. 2. Enforce a strict Content Security Policy (CSP) that disallows inline scripts and restricts script sources to trusted domains, preventing execution of injected JavaScript. 3. Limit editor privileges strictly to trusted personnel and implement multi-factor authentication (MFA) for editor accounts to reduce risk of account compromise. 4. Conduct regular security audits and code reviews of CMS content inputs to detect and sanitize potentially malicious content. 5. Monitor web application logs for unusual editor activity or injection attempts. 6. Educate content editors about the risks of injecting untrusted content and enforce input validation at the application level. 7. Implement Web Application Firewall (WAF) rules to detect and block common XSS payloads targeting the CMS. 8. Regularly review and update security policies related to CSP and user privilege management to maintain defense-in-depth.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-02T15:43:16.585Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692f388ae0601f8fcd7a9506

Added to database: 12/2/2025, 7:05:46 PM

Last enriched: 12/2/2025, 7:21:13 PM

Last updated: 12/4/2025, 11:22:42 PM

Views: 46

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