CVE-2025-64622

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 visit 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 platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged user access to vulnerable form fields. AEM instances with custom form components may have additional attack surfaces.

📦 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

Low-privileged users could escalate privileges, steal session data from other users, or perform limited client-side attacks.

🟢

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 authenticated low-privileged access. The vulnerability is in form fields where user input is not properly sanitized.

🛠️ 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's distribution portal. 2. Follow Adobe's upgrade documentation for your deployment type (on-premise or cloud). 3. Apply the update package. 4. Restart AEM services. 5. Verify the update completed successfully.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize form field input before processing

Implement Java servlet filter with OWASP Java Encoder library for XSS prevention

Content Security Policy

all

Deploy strict CSP headers to mitigate script execution even if injection occurs

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

🧯 If You Can't Patch

  • Restrict low-privileged user access to form editing capabilities
  • Implement web application firewall rules to block XSS payload patterns

🔍 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 basic XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags
  • Multiple failed XSS attempts in request logs
  • Suspicious content authoring activity

Network Indicators:

  • HTTP requests containing script payloads in form parameters
  • Unusual outbound connections from AEM to external domains

SIEM Query:

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

🔗 References

📤 Share & Export