CVE-2025-64794

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.23 and earlier contain a stored XSS vulnerability where low-privileged attackers can inject malicious scripts into form fields. When victims browse 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.23 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged attacker access to vulnerable form fields; affects both authoring and publishing instances.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, perform actions as authenticated users, deface websites, or redirect users to malicious sites, potentially leading to full account compromise and data theft.

🟠

Likely Case

Attackers with low privileges inject malicious scripts to steal session tokens or credentials from other users, enabling unauthorized access to sensitive content management functions.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized, preventing execution while maintaining normal functionality.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires low-privileged access to inject scripts; typical XSS techniques apply.

🛠️ 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+ from Adobe Distribution. 2. Backup current instance. 3. Apply update via Package Manager. 4. Restart AEM services. 5. Verify update via /system/console/status-productinfo.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize form field inputs before processing.

Implement Java filter with OWASP Java Encoder library for XSS prevention

Content Security Policy

all

Deploy strict CSP headers to restrict script execution sources.

Add 'Content-Security-Policy: script-src 'self'' to HTTP responses

🧯 If You Can't Patch

  • Restrict low-privileged user access to vulnerable form fields via ACLs
  • Implement WAF rules to block XSS payload patterns in form submissions

🔍 How to Verify

Check if Vulnerable:

Check AEM version via /system/console/status-productinfo; if version ≤6.5.23, instance is vulnerable.

Check Version:

curl -k https://<aem-host>:<port>/system/console/status-productinfo | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify version is ≥6.5.24 and test form fields with XSS payloads (e.g., <script>alert('test')</script>) to ensure sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form endpoints with script tags
  • Error logs showing script injection attempts

Network Indicators:

  • HTTP requests containing <script> tags in form parameters
  • Unusual outbound connections from AEM to external domains

SIEM Query:

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

🔗 References

📤 Share & Export