CVE-2025-64861

5.4 MEDIUM

📋 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 Adobe Experience Manager versions 6.5.23 and earlier are affected.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.23 and earlier
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged attacker access to vulnerable form fields

📦 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 elevate their access, steal user session data, or perform limited malicious actions within the application context.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented, though the underlying code flaw would still exist.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

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 Adobe Experience Manager 6.5.24 or later from Adobe's official distribution. 2. Follow Adobe's upgrade documentation for your deployment type (on-premise or cloud). 3. Apply the update to all affected instances. 4. Restart the AEM service.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize form field inputs

Implement custom servlet filter or use AEM's built-in XSS protection features

Content Security Policy

all

Implement strict CSP headers to limit script execution

Add Content-Security-Policy header to AEM dispatcher configuration

🧯 If You Can't Patch

  • Restrict low-privileged user access to form editing capabilities
  • Implement web application firewall rules to detect and block XSS payloads

🔍 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-productinfo

Verify Fix Applied:

After patching, verify version is 6.5.24 or later and test form fields with XSS payloads to ensure they're properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags
  • Multiple failed XSS attempts in request logs
  • Suspicious content node creations

Network Indicators:

  • HTTP requests containing script tags in form parameters
  • Unusual POST requests to form submission endpoints

SIEM Query:

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

🔗 References

📤 Share & Export