CVE-2025-64627

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 users visit pages containing the compromised fields, their browsers execute the attacker's code. 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 supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both author and publish instances. Requires attacker to have at least low-privileged access to create or edit content.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, perform actions as authenticated users, redirect users to malicious sites, or deploy additional malware payloads.

🟠

Likely Case

Attackers with low privileges could deface content, steal user session data from other low-privileged users, or perform limited unauthorized actions within the application.

🟢

If Mitigated

With proper input validation and output encoding controls, the vulnerability would be prevented from executing malicious scripts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Requires authenticated access but only low privileges. Exploitation involves injecting JavaScript into vulnerable form fields that persists in the system.

🛠️ 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. Apply the service pack following Adobe's upgrade documentation. 3. Restart all AEM instances. 4. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize user input in form fields

Implement Java servlet filter with OWASP Java Encoder library for input sanitization

Content Security Policy

all

Implement strict CSP headers to restrict script execution

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

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Restrict low-privileged user access to content creation/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 basic XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content creation/modification by low-privileged users
  • Requests containing script tags or JavaScript in form parameters

Network Indicators:

  • HTTP requests with suspicious script payloads in POST data
  • Unexpected outbound connections from AEM servers

SIEM Query:

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

🔗 References

📤 Share & Export