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

0
Medium
VulnerabilityCVE-2025-64790cvecve-2025-64790cwe-79
Published: Wed Dec 10 2025 (12/10/2025, 18:23:04 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/17/2025, 19:45:29 UTC

Technical Analysis

CVE-2025-64790 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability arises from insufficient sanitization of user-supplied input in certain form fields, allowing a low-privileged attacker to inject malicious JavaScript code that is stored persistently 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 AEM instance. This can lead to unauthorized actions such as session hijacking, credential theft, or manipulation of displayed content, impacting confidentiality and integrity. The vulnerability requires the attacker to have some level of access to submit input (low privilege) and relies on user interaction to trigger the malicious script execution. The CVSS v3.1 base score is 5.4, indicating medium severity, with vector metrics AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, meaning network attack vector, low attack complexity, low privileges required, user interaction required, scope changed, and partial confidentiality and integrity impact without availability impact. No public exploit code or active exploitation has been reported yet. Adobe has not yet released a patch at the time of this report, so organizations must rely on interim mitigations. This vulnerability is significant because AEM is widely used by enterprises for managing web content and digital experiences, making it a valuable target for attackers aiming to compromise user sessions or deface content.

Potential Impact

For European organizations, the impact of CVE-2025-64790 can be substantial, especially for those relying on Adobe Experience Manager for their digital content management and customer-facing portals. Exploitation could lead to theft of user credentials, session tokens, or other sensitive information, potentially enabling further unauthorized access or data breaches. The integrity of web content could be compromised, damaging brand reputation and user trust. Since AEM often hosts critical corporate websites and intranet portals, the vulnerability could disrupt business operations indirectly through reputational harm or regulatory scrutiny under GDPR if personal data is exposed. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in environments with many users or where attackers can lure victims to vulnerable pages. The medium severity score reflects these factors, but the scope change (S:C) indicates that the vulnerability can affect resources beyond the initially compromised component, increasing potential impact. Organizations in sectors such as finance, government, and media, which heavily use AEM, may face higher risks.

Mitigation Recommendations

To mitigate CVE-2025-64790, European organizations should implement the following specific measures: 1) Apply input validation and output encoding on all user-supplied data in AEM forms to prevent injection of malicious scripts. 2) Restrict user privileges to the minimum necessary, limiting the ability of low-privileged users to submit content that could be malicious. 3) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4) Monitor web server and application logs for unusual input patterns or repeated attempts to inject scripts. 5) Educate users about the risks of interacting with suspicious links or content within the organization’s web portals. 6) Isolate AEM instances from critical internal networks to reduce lateral movement risk if exploitation occurs. 7) Stay updated with Adobe security advisories and apply patches promptly once available. 8) Consider deploying web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting AEM. These steps go beyond generic advice by focusing on the specific context of AEM and the nature of the vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

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

Threat ID: 6939bdb1fe7b3954b690bbec

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

Last enriched: 12/17/2025, 7:45:29 PM

Last updated: 2/7/2026, 2:27:33 AM

Views: 52

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats