CVE-2025-64875

5.4 MEDIUM

📋 TL;DR

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into vulnerable form fields. When victims browse pages containing these fields, their browsers execute the attacker's scripts. This affects Adobe Experience Manager versions 6.5.23 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.23 and earlier
Operating Systems: All platforms running Adobe Experience Manager
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 session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware on victim systems.

🟠

Likely Case

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

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation 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 and restart the AEM service.

🔧 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 in web server configuration

Input Validation and Output Encoding

all

Implement server-side validation and proper output encoding for all user inputs.

Configure AEM to use OWASP Java Encoder or similar libraries for output encoding

🧯 If You Can't Patch

  • Restrict low-privileged user access to form editing capabilities
  • Implement web application firewall (WAF) rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check Adobe Experience Manager version via AEM Web Console (/system/console/status-productinfo) or CRX Package Manager.

Check Version:

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

Verify Fix Applied:

Verify version is 6.5.24 or later and test form fields with XSS payloads to confirm they're properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript code
  • Multiple failed XSS attempts in request logs

Network Indicators:

  • HTTP requests containing common XSS payload patterns to form endpoints

SIEM Query:

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

🔗 References

📤 Share & Export