Skip to main content

CVE-2025-47077: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager

Medium
VulnerabilityCVE-2025-47077cvecve-2025-47077cwe-79
Published: Tue Jun 10 2025 (06/10/2025, 22:20:31 UTC)
Source: CVE Database V5
Vendor/Project: Adobe
Product: Adobe Experience Manager

Description

Adobe Experience Manager versions 6.5.22 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: 07/11/2025, 06:46:30 UTC

Technical Analysis

CVE-2025-47077 is a stored Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.22 and earlier. This vulnerability allows a low-privileged attacker to inject malicious JavaScript code into vulnerable form fields within the AEM interface. When a victim user accesses a page containing the injected malicious script, the script executes in their browser context. Stored XSS differs from reflected XSS in that the malicious payload is permanently stored on the server (e.g., in a database or content repository) and served to multiple users, increasing the attack's persistence and impact. The vulnerability arises due to insufficient input validation or output encoding of user-supplied data in form fields, enabling script injection. The CVSS 3.1 base score is 5.4 (medium severity), reflecting that the attack vector is network-based (AV:N), requires low privileges (PR:L), and user interaction (UI:R) to trigger the script execution. The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality and integrity (C:L/I:L) but not availability (A:N). No known exploits are currently reported in the wild, and no patches have been linked yet. However, given the widespread use of Adobe Experience Manager in enterprise content management and web content delivery, this vulnerability could be leveraged to steal session tokens, perform actions on behalf of users, or deliver further malware payloads via the victim's browser.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on Adobe Experience Manager for managing public-facing websites, intranets, or digital marketing platforms. Successful exploitation could lead to unauthorized access to sensitive user information, session hijacking, or defacement of web content, damaging brand reputation and customer trust. Since AEM is often used by large enterprises, government agencies, and public institutions in Europe, the risk extends to critical sectors such as finance, healthcare, and public administration. The stored XSS could also be used as a foothold for more complex attacks, including phishing campaigns targeting employees or customers. Additionally, compliance with GDPR and other data protection regulations may be jeopardized if personal data is exposed or manipulated through this vulnerability, potentially resulting in legal and financial penalties.

Mitigation Recommendations

European organizations should prioritize the following specific mitigation steps: 1) Immediately audit all AEM instances to identify usage of vulnerable versions (6.5.22 and earlier). 2) Apply official Adobe patches or updates as soon as they become available; if patches are delayed, consider temporary workarounds such as disabling or restricting vulnerable form fields. 3) Implement strict input validation and output encoding on all user-supplied data in AEM forms to prevent script injection. 4) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 5) Conduct regular security testing, including automated scanning and manual penetration tests focused on XSS vulnerabilities within AEM deployments. 6) Educate web administrators and developers on secure coding practices specific to AEM. 7) Monitor web server and application logs for suspicious activity indicative of attempted exploitation. 8) Limit user privileges within AEM to the minimum necessary to reduce the risk posed by low-privileged attackers. 9) Consider deploying Web Application Firewalls (WAFs) with rules targeting XSS payloads to provide an additional layer of defense.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
adobe
Date Reserved
2025-04-30T20:47:54.999Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6848b19b3cd93dcca831209c

Added to database: 6/10/2025, 10:28:43 PM

Last enriched: 7/11/2025, 6:46:30 AM

Last updated: 8/14/2025, 3:32:11 PM

Views: 17

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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