CVE-2025-64619

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 AEM versions 6.5.23 and earlier.

💻 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 attacker access to vulnerable form fields; affects both author and publish instances.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, perform session hijacking, deface websites, or redirect users to malicious sites, potentially leading to full system compromise.

🟠

Likely Case

Attackers with low privileges steal session cookies or user data from other users browsing affected pages, enabling account takeover or data theft.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts are neutralized before execution, preventing successful exploitation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated low-privileged access; stored XSS allows persistent attacks across user sessions.

🛠️ 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. 2. Backup current installation. 3. Apply the update following Adobe's upgrade documentation. 4. Restart AEM services.

🔧 Temporary Workarounds

Input Validation Filter

all

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

Configure AEM's XSS protection filters via OSGi configuration

Content Security Policy

all

Implement CSP headers to restrict script execution sources.

Add 'Content-Security-Policy' header to web server configuration

🧯 If You Can't Patch

  • Restrict low-privileged user access to content creation/modification features
  • Implement web application firewall rules to block XSS payloads

🔍 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

Verify Fix Applied:

After patching, verify version is 6.5.24 or later and test form fields with XSS payloads to ensure sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form submission endpoints with script tags
  • Error logs showing XSS filter violations

Network Indicators:

  • HTTP requests containing JavaScript payloads in form parameters

SIEM Query:

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

🔗 References

📤 Share & Export