CVE-2025-64857

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 scripts into form fields. When users visit pages containing these compromised fields, their browsers execute the attacker's JavaScript, 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: Affects all deployment types (on-premise, cloud, hybrid) with vulnerable form fields.

📦 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 install malware through drive-by downloads.

🟠

Likely Case

Low-privileged attackers steal session cookies of regular users, potentially escalating privileges or accessing sensitive data 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 low-privileged attacker access to inject scripts into 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 Adobe Experience Manager 6.5.24 or later from Adobe's distribution portal. 2. Follow Adobe's upgrade documentation for your deployment type. 3. Apply the update to all instances. 4. Restart all AEM services. 5. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize form field inputs before processing.

Configure AEM's XSS protection filters in /system/console/configMgr

Content Security Policy

all

Implement strict Content Security Policy headers to restrict script execution.

Add CSP headers via Apache/Dispatcher configuration or AEM filters

🧯 If You Can't Patch

  • Restrict low-privileged user access to vulnerable form fields and components.
  • 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. If version is 6.5.23 or earlier, system is vulnerable.

Check Version:

curl -u admin:password http://localhost:4502/system/console/status-productinfo.json | grep version

Verify Fix Applied:

After patching, verify version is 6.5.24 or later and test form fields with XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form endpoints with script tags or JavaScript payloads
  • Multiple failed login attempts followed by form submissions

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 "onload=" OR "onerror=")

🔗 References

📤 Share & Export