CVE-2025-64873

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting 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 scripts, 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. All deployment types (on-premise, cloud) are affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, compromise user accounts, redirect users to malicious sites, or perform actions on behalf of authenticated users.

🟠

Likely Case

Low-privileged attackers steal session cookies or credentials from users who view compromised pages, leading to account takeover.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented despite the underlying code flaw.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires low-privileged access to vulnerable form fields. The vulnerability is in the web interface components.

🛠️ 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. Follow Adobe's upgrade documentation for your deployment type. 3. Apply the update to all instances. 4. Restart all AEM services. 5. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize user input in form fields

Implement custom servlet filter or use Adobe's security filters to sanitize input

Content Security Policy

all

Implement strict Content Security Policy headers to limit script execution

Add 'Content-Security-Policy' header with script-src directives

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Restrict low-privileged user access to content 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 | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify version is 6.5.24 or later. Test form fields with safe XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content modifications in form fields
  • Multiple failed XSS attempts in request logs
  • Suspicious script tags in content submissions

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form parameters
  • Unusual outbound connections from user browsers after visiting AEM pages

SIEM Query:

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

🔗 References

📤 Share & Export