CVE-2025-64549
📋 TL;DR
This stored XSS vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing the injected scripts, their browsers execute the malicious code. Organizations using AEM versions 6.5.23 and earlier are affected.
💻 Affected Systems
- Adobe Experience Manager
📦 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
Attackers with low privileges could escalate privileges, steal user session data, or perform limited malicious actions within the application context.
If Mitigated
With proper input validation and output encoding, the impact is minimal as malicious scripts would be properly sanitized.
🎯 Exploit Status
Requires authenticated low-privileged access to vulnerable form fields
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 6.5.24 or later
Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb25-115.html
Restart Required: Yes
Instructions:
1. Download AEM 6.5.24 or later from Adobe's distribution portal. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart AEM instances. 4. Verify the update was successful.
🔧 Temporary Workarounds
Input Validation Filter
allImplement custom servlet filters to sanitize user input in form fields
Content Security Policy
allImplement strict CSP headers to restrict script execution
🧯 If You Can't Patch
- Implement web application firewall rules to block XSS payloads
- Restrict low-privileged user access to content editing capabilities
🔍 How to Verify
Check if Vulnerable:
Check AEM version via CRXDE Lite or system console. If version is 6.5.23 or earlier, system is vulnerable.Check Version:
curl -u admin:admin http://localhost:4502/system/console/status-productinfoVerify Fix Applied:
Verify AEM version is 6.5.24 or later and test form fields with XSS payloads to ensure sanitization.📡 Detection & Monitoring
Log Indicators:
- Unusual content modifications by low-privileged users
- JavaScript payloads in request logs
Network Indicators:
- Suspicious script tags in HTTP requests to form endpoints
SIEM Query:
source="aem-access.log" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")