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

0
Medium
VulnerabilityCVE-2025-64580cvecve-2025-64580cwe-79
Published: Wed Dec 10 2025 (12/10/2025, 18:23:40 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:14:01 UTC

Technical Analysis

CVE-2025-64580 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM), a widely used enterprise content management system. This vulnerability affects versions 6.5.23 and earlier. The flaw allows a low-privileged attacker to inject malicious JavaScript code into form fields that are not properly sanitized or validated. When legitimate users access pages containing these injected scripts, the malicious code executes in their browsers under the context of the vulnerable web application. This can lead to unauthorized actions such as session hijacking, theft of sensitive information, or manipulation of displayed content. The vulnerability requires the attacker to have some level of access to submit data (low privilege) and relies on user interaction to trigger the payload execution. The CVSS 3.1 base score is 5.4, indicating a medium severity level, with attack vector being network-based, low attack complexity, requiring privileges, and user interaction. The scope is changed, meaning the vulnerability can affect resources beyond the initially vulnerable component. No public exploits have been reported yet, but the risk remains significant due to the widespread use of AEM in enterprise environments. The absence of available patches at the time of reporting necessitates immediate mitigation through input validation and security controls.

Potential Impact

For European organizations, this vulnerability poses a risk to the confidentiality and integrity of web applications managed via Adobe Experience Manager. Attackers exploiting this flaw could steal session cookies, enabling unauthorized access to user accounts or administrative functions, potentially leading to data breaches or unauthorized content modifications. The impact is particularly critical for organizations handling sensitive or regulated data, such as financial institutions, healthcare providers, and government agencies. Since AEM is commonly used for public-facing websites and intranet portals, exploitation could damage organizational reputation and trust. The requirement for user interaction and low privileges reduces the likelihood of widespread automated exploitation but does not eliminate targeted attacks. The vulnerability could also facilitate phishing or social engineering campaigns by injecting deceptive content into trusted sites. Overall, the threat could disrupt business operations and compliance with European data protection regulations like GDPR if exploited.

Mitigation Recommendations

European organizations should prioritize the following specific mitigation steps: 1) Monitor Adobe's security advisories closely and apply official patches or updates for AEM as soon as they become available. 2) Implement strict input validation and sanitization on all form fields to prevent injection of malicious scripts, using server-side validation in addition to client-side checks. 3) Deploy and enforce a robust Content Security Policy (CSP) to restrict execution of unauthorized scripts and reduce the impact of XSS attacks. 4) Conduct regular security audits and penetration testing focused on web application vulnerabilities, including XSS. 5) Use web application firewalls (WAFs) configured to detect and block common XSS attack patterns targeting AEM. 6) Educate users and administrators about the risks of XSS and encourage cautious behavior when interacting with web content. 7) Review and limit user privileges to the minimum necessary to reduce the attack surface. 8) Monitor web server and application logs for suspicious input patterns or repeated failed attempts to inject scripts. These measures, combined, will help reduce the risk until a patch is applied.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
adobe
Date Reserved
2025-11-05T22:51:33.028Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6939bda9fe7b3954b690b312

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

Last enriched: 12/10/2025, 7:14:01 PM

Last updated: 12/11/2025, 7:09:15 AM

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