CVE-2025-64845

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.23 and earlier contain a stored cross-site scripting vulnerability in form fields. Low-privileged attackers can inject malicious JavaScript that executes in victims' browsers when they view compromised pages. 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 authenticated low-privileged user 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

Session hijacking, credential theft, or unauthorized content modification by authenticated low-privileged users.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated access to vulnerable form fields. Attack complexity is low once access is obtained.

🛠️ 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 distribution portal. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart AEM instance. 4. Verify successful installation via AEM welcome screen.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources

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

Input Validation Filter

all

Implement server-side input validation for all form fields

Configure AEM filters to sanitize user input before processing

🧯 If You Can't Patch

  • Restrict low-privileged user access to content editing interfaces
  • Implement web application firewall rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via Welcome screen or CRXDE. Versions 6.5.23 and earlier are vulnerable.

Check Version:

Check AEM welcome screen at /libs/cq/core/content/welcome.html or use CRXDE to check version properties

Verify Fix Applied:

Verify AEM version is 6.5.24 or later and test form fields with XSS payloads.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content modifications by low-privileged users
  • JavaScript payloads in content update requests

Network Indicators:

  • Suspicious script tags in HTTP POST requests to content endpoints

SIEM Query:

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

🔗 References

📤 Share & Export