CVE-2025-64792

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.23 and earlier contain a stored XSS vulnerability that allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing the compromised fields, their browsers execute the attacker's code, 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: Requires low-privileged attacker access to vulnerable form fields; affects both author and publish instances.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator sessions, compromise user accounts, deface websites, or redirect users to malicious sites, potentially leading to full system compromise.

🟠

Likely Case

Low-privileged attackers steal session cookies or credentials from users who view compromised pages, enabling account takeover and lateral movement.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts are neutralized, preventing execution while maintaining form functionality.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated low-privileged access; stored XSS allows persistent attacks affecting multiple users.

🛠️ 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. Apply the service pack following Adobe's installation guide. 3. Restart all AEM instances. 4. Verify the update completed successfully.

🔧 Temporary Workarounds

Input Validation Filter

all

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

Configure AEM's XSS protection filters via OSGi console or repository configuration

Content Security Policy

all

Implement CSP headers to restrict script execution from unauthorized sources.

Add 'Content-Security-Policy' header via dispatcher or web server configuration

🧯 If You Can't Patch

  • Restrict low-privileged user access to form creation and 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:password http://localhost:4502/system/console/status-productinfo | grep 'Adobe Experience Manager'

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 or JavaScript code in request parameters
  • Multiple failed XSS attempts in request logs

Network Indicators:

  • HTTP requests containing script tags or JavaScript in POST data to form endpoints

SIEM Query:

source="aem_logs" AND ("<script" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export