CVE-2025-47033

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.22 and earlier contain a stored cross-site scripting vulnerability that allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing the compromised fields, their browsers execute the attacker's scripts, potentially leading to session hijacking or data theft.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged attacker access to vulnerable form fields

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, perform actions as authenticated users, deface websites, or redirect users to malicious sites.

🟠

Likely Case

Low-privileged attackers inject malicious scripts to steal user session data or perform limited unauthorized actions within the application.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented, though the underlying code flaw remains.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Requires authenticated low-privileged access to vulnerable form fields

🛠️ 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 deployment type (on-premise or cloud). 3. Apply the update to all affected instances. 4. Restart the AEM service.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize user input in form fields

Configure AEM's XSS protection filters via OSGi configuration

Content Security Policy

all

Implement strict CSP headers to limit script execution

Add Content-Security-Policy headers via dispatcher or web server configuration

🧯 If You Can't Patch

  • Restrict low-privileged user access to vulnerable form fields and components
  • Implement web application firewall rules to detect and block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via the Welcome screen or CRXDE Lite interface

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

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form submission endpoints with script tags
  • Multiple failed XSS attempts in request logs

Network Indicators:

  • HTTP requests containing script injection patterns to AEM endpoints

SIEM Query:

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

🔗 References

📤 Share & Export