CVE-2025-47071

5.4 MEDIUM

📋 TL;DR

A stored cross-site scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into vulnerable form fields. When victims browse pages containing the compromised fields, their browsers execute the attacker's scripts. This affects AEM versions 6.5.22 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged attacker access to vulnerable form fields. AEM as a Cloud Service is not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware through drive-by downloads.

🟠

Likely Case

Session hijacking, credential theft, or defacement of web pages through injected content.

🟢

If Mitigated

Limited impact with proper input validation, output encoding, and Content Security Policy (CSP) headers in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated low-privileged access. Stored XSS vulnerabilities are commonly exploited in real-world attacks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.23 or later

Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb25-48.html

Restart Required: Yes

Instructions:

1. Download AEM 6.5.23 or later from Adobe's distribution portal. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart the AEM instance. 4. Verify the update completed successfully.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources and prevent XSS payloads from running.

Add 'Content-Security-Policy' header with appropriate directives in web server configuration

Input Validation and Output Encoding

all

Implement server-side validation and proper output encoding for all user inputs in form fields.

Configure AEM components to use HTL (Sightly) automatic context-aware escaping

🧯 If You Can't Patch

  • Restrict low-privileged user access to content authoring and form submission capabilities
  • Implement web application firewall (WAF) rules to detect and block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via OSGi console (http://[host]:[port]/system/console/bundles) or CRX Package Manager. If version is 6.5.22 or earlier, system is vulnerable.

Check Version:

curl -s http://localhost:4502/system/console/bundles | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify version is 6.5.23 or later. Test form fields with safe XSS payloads to confirm proper sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content submissions containing script tags or JavaScript code in form fields
  • Multiple failed validation attempts on form inputs

Network Indicators:

  • HTTP requests with suspicious parameters containing script tags or JavaScript functions

SIEM Query:

source="aem-access.log" AND ("<script" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export