CVE-2025-64550

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.23 and earlier contain a DOM-based Cross-Site Scripting vulnerability that allows low-privileged attackers to execute malicious JavaScript in victims' browsers. Exploitation requires user interaction such as clicking a crafted link. 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
Default Config Vulnerable: ⚠️ Yes
Notes: Requires user interaction for exploitation. Low-privileged users can exploit this vulnerability.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware through the victim's browser.

🟠

Likely Case

Session hijacking, credential theft, or defacement of web content through injected scripts.

🟢

If Mitigated

Limited impact with proper Content Security Policy headers and input validation in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires user interaction and low-privileged access. DOM-based XSS typically requires specific user actions.

🛠️ 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 the AEM instance. 4. Verify the update was successful.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution from untrusted sources

Add 'Content-Security-Policy' header with appropriate directives to web server configuration

Input Validation Filter

all

Implement server-side validation for all user inputs

Configure AEM filters to sanitize user inputs before processing

🧯 If You Can't Patch

  • Restrict low-privileged user access to AEM authoring interfaces
  • Implement web application firewall rules to detect and block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via the welcome page or OSGi console. Versions 6.5.23 and earlier are vulnerable.

Check Version:

curl -k https://aem-instance:4502/libs/granite/core/content/login.html | grep 'AEM 6.5'

Verify Fix Applied:

Verify AEM version is 6.5.24 or later and test for XSS using security scanning tools.

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript payloads in request logs
  • Multiple failed login attempts from same IP
  • Suspicious URL parameters containing script tags

Network Indicators:

  • HTTP requests with encoded script payloads in parameters
  • Unusual outbound connections from AEM server

SIEM Query:

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

🔗 References

📤 Share & Export