CVE-2025-46910

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.22 and earlier contain a stored XSS vulnerability where low-privileged attackers can inject malicious scripts into form fields. When users visit pages containing these compromised fields, their browsers execute the attacker's JavaScript. This affects organizations using vulnerable AEM instances for content management.

💻 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. 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 deploy additional malware payloads through the compromised browser sessions.

🟠

Likely Case

Session hijacking, credential theft, or defacement of web content through injected scripts that execute in victims' 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-privilege access. Exploitation involves injecting scripts into vulnerable form fields that persist and execute when viewed.

🛠️ 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. Backup your AEM instance. 2. Download and apply AEM 6.5.23 or later from Adobe's distribution portal. 3. Follow Adobe's upgrade documentation for your specific deployment. 4. Restart the AEM service. 5. Verify the update completed successfully.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources and prevent inline script execution.

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

Input Validation and Output Encoding

all

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

Configure AEM's XSS protection filters and implement custom validation servlets

🧯 If You Can't Patch

  • Restrict low-privileged user access to content creation/modification 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 CRXDE Lite. Verify if version is 6.5.22 or earlier.

Check Version:

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

Verify Fix Applied:

Confirm AEM version is 6.5.23 or later. Test form fields with safe XSS payloads to ensure they're properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content modifications by low-privileged users
  • Script tags or JavaScript patterns in content update requests

Network Indicators:

  • HTTP requests containing script injection patterns to form submission endpoints

SIEM Query:

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

🔗 References

📤 Share & Export