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-64817: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager

0
Medium
VulnerabilityCVE-2025-64817cvecve-2025-64817cwe-79
Published: Wed Dec 10 2025 (12/10/2025, 18:24:09 UTC)
Source: CVE Database V5
Vendor/Project: Adobe
Product: Adobe Experience Manager

Description

Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

AI-Powered Analysis

AILast updated: 12/10/2025, 19:00:22 UTC

Technical Analysis

CVE-2025-64817 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability arises due to insufficient sanitization of user-supplied input in certain form fields, allowing a low-privileged attacker to inject malicious JavaScript code that is stored on the server. When other users access the affected pages containing the injected scripts, the malicious code executes in their browsers within the security context of the vulnerable site. This can lead to unauthorized actions such as session hijacking, defacement, or redirection to malicious sites, impacting confidentiality and integrity of user data. The vulnerability requires the attacker to have some level of access to submit data (low privilege) and relies on user interaction to trigger the script execution. The CVSS 3.1 score of 5.4 reflects a medium severity, with network attack vector, low attack complexity, and partial confidentiality and integrity impact, but no availability impact. No public exploits have been reported yet, but the vulnerability is published and should be addressed promptly. Adobe Experience Manager is widely used by enterprises for web content management, making this vulnerability relevant for organizations relying on AEM for digital experience delivery. The lack of an official patch link suggests mitigation may currently rely on configuration changes or custom input validation until Adobe releases an update.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those using Adobe Experience Manager to manage public-facing websites or internal portals. Exploitation could lead to theft of user credentials, session tokens, or sensitive information, enabling further compromise of user accounts or internal systems. It may also facilitate phishing attacks or malware distribution by injecting malicious scripts into trusted web pages. This can damage organizational reputation, lead to regulatory non-compliance (e.g., GDPR breaches due to data exposure), and cause operational disruptions. The medium severity score indicates a moderate risk, but the widespread use of AEM in sectors like government, finance, and retail across Europe increases the potential attack surface. Additionally, attackers could leverage this vulnerability as a foothold for more sophisticated attacks within the network. The requirement for user interaction and low privilege reduces the likelihood of mass exploitation but does not eliminate targeted attacks against high-value European entities.

Mitigation Recommendations

1. Immediately review and restrict user input on all forms within Adobe Experience Manager to ensure proper input validation and sanitization, preventing malicious script injection. 2. Implement robust output encoding on all user-supplied content rendered in web pages to neutralize any injected scripts. 3. Limit the privileges of users who can submit data to forms, applying the principle of least privilege to reduce attack vectors. 4. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing AEM-managed sites. 5. Monitor web application logs for unusual input patterns or repeated failed attempts to inject scripts. 6. Until an official Adobe patch is available, consider disabling or restricting vulnerable form functionalities if feasible. 7. Educate users about the risks of interacting with suspicious content and encourage reporting of anomalous website behavior. 8. Plan for timely deployment of Adobe security updates once released, and test patches in staging environments before production rollout. 9. Conduct regular security assessments and penetration testing focused on web application vulnerabilities including XSS.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
adobe
Date Reserved
2025-11-11T22:48:38.830Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6939bdb3fe7b3954b690be6d

Added to database: 12/10/2025, 6:36:35 PM

Last enriched: 12/10/2025, 7:00:22 PM

Last updated: 12/11/2025, 3:47:54 AM

Views: 4

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