CVE-2025-64548

5.4 MEDIUM

📋 TL;DR

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

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.23 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged user access to vulnerable form fields; web applications using affected AEM instances are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, perform actions as authenticated users, redirect users to malicious sites, or deploy additional malware payloads.

🟠

Likely Case

Low-privileged users could elevate privileges by stealing session tokens, deface content, or perform limited data exfiltration from user browsers.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented, though legacy systems without patches remain at risk.

🌐 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 typically has straightforward exploitation paths once vulnerable fields are identified.

🛠️ 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. Backup your AEM instance. 2. Download and apply the latest service pack (6.5.24+). 3. Restart the AEM service. 4. Verify the update completed successfully.

🔧 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 CSP headers to restrict script execution

Add 'Content-Security-Policy' header to AEM dispatcher configuration

🧯 If You Can't Patch

  • Restrict low-privileged user access to content authoring interfaces
  • Implement web application firewall rules to block XSS payload patterns

🔍 How to Verify

Check if Vulnerable:

Check AEM version via CRXDE Lite or system console; versions 6.5.23 or earlier are vulnerable

Check Version:

curl -u admin:password http://localhost:4502/system/console/status-productinfo

Verify Fix Applied:

Verify version is 6.5.24 or later and test form fields for XSS payload acceptance

📡 Detection & Monitoring

Log Indicators:

  • Unusual content modifications by low-privileged users
  • JavaScript payloads in request logs to form endpoints

Network Indicators:

  • Suspicious script tags in HTTP POST requests to AEM authoring interfaces

SIEM Query:

source="aem_logs" AND ("script" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export