CVE-2025-47091

5.4 MEDIUM

📋 TL;DR

This 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 all users of Adobe Experience Manager 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. All deployment types (on-premise, cloud) are 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 on victim systems.

🟠

Likely Case

Session hijacking, credential theft, defacement of web pages, or data exfiltration from user browsers.

🟢

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

Requires authenticated low-privileged access. Exploitation involves injecting JavaScript into vulnerable form fields that persists in the system.

🛠️ 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 Adobe Experience Manager 6.5.23 or later from Adobe's official distribution channels. 2. Follow Adobe's upgrade documentation for your specific deployment type. 3. Apply the update to all affected instances. 4. Restart the AEM service. 5. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and proper output encoding for all user-controllable form fields.

Implement in application code: Use OWASP ESAPI or similar libraries for output encoding

Content Security Policy (CSP)

all

Deploy strict CSP headers to limit script execution sources and prevent inline script execution.

Add to web server config: Content-Security-Policy: script-src 'self'

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to block XSS payloads in form submissions
  • Restrict low-privileged user access to content authoring and form submission capabilities

🔍 How to Verify

Check if Vulnerable:

Check AEM version via AEM Web Console (/system/console) or by examining the AEM installation directory for version files.

Check Version:

curl -k https://<aem-host>:<port>/system/console/status-productinfo | grep 'Adobe Experience Manager'

Verify Fix Applied:

Verify version is 6.5.23 or later and test form fields with XSS payloads to ensure they are properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript code
  • Multiple failed XSS attempts in access logs

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form parameters
  • Unusual outbound connections from user browsers after visiting AEM pages

SIEM Query:

source="aem_access.log" AND ("<script" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export