CVE-2025-64797

5.4 MEDIUM

📋 TL;DR

This stored 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. 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 supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Requires attacker to have low-privileged 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 steal session tokens from other users, perform limited actions within their permission scope, or deploy credential harvesting pages.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized before reaching victim browsers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated low-privileged access and knowledge of 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. Restart all AEM instances after applying the update.

🔧 Temporary Workarounds

Input Validation Filter

all

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

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

Content Security Policy

all

Deploy strict Content Security Policy headers to limit script execution.

Add 'Content-Security-Policy: script-src 'self'' to HTTP responses

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads in form submissions
  • Review and restrict low-privileged user access to form editing capabilities

🔍 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.json | 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 containing script tags or JavaScript code
  • Multiple failed XSS attempts in request logs

Network Indicators:

  • HTTP requests containing script tags in form parameters
  • Unusual outbound connections from AEM instances

SIEM Query:

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

🔗 References

📤 Share & Export