CVE-2025-64790

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 Adobe Experience Manager versions 6.5.23 and earlier.

💻 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; specific fields not disclosed in advisory.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware on victim systems.

🟠

Likely Case

Session hijacking, credential theft, or defacement of web pages through injected content.

🟢

If Mitigated

Limited impact with proper input validation and output encoding in place, though risk remains if vulnerable fields are exposed.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires low-privileged access to inject scripts; stored XSS typically has straightforward exploitation once vulnerable fields are identified.

🛠️ 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 to apply the patch. 3. Restart the AEM instance to ensure changes take effect.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and output encoding for all user-controllable form fields to prevent script injection.

Content Security Policy (CSP)

all

Deploy a strict Content Security Policy to mitigate XSS impact by restricting script execution sources.

🧯 If You Can't Patch

  • Restrict low-privileged user access to form fields and administrative interfaces.
  • Monitor and audit user inputs in form fields for suspicious script patterns.

🔍 How to Verify

Check if Vulnerable:

Check Adobe Experience Manager version via AEM Web Console (/system/console/status-productinfo) or by reviewing installation logs.

Check Version:

curl -k https://<aem-host>:<port>/system/console/status-productinfo | grep 'Adobe Experience Manager'

Verify Fix Applied:

Confirm version is 6.5.24 or later and test form fields for XSS by attempting to inject benign scripts (e.g., <script>alert('test')</script>) in a controlled environment.

📡 Detection & Monitoring

Log Indicators:

  • Unusual script tags or JavaScript in form submissions in AEM logs
  • Multiple failed login attempts followed by form field modifications

Network Indicators:

  • HTTP requests containing script payloads to AEM endpoints
  • Unexpected redirects or external resource loads from AEM pages

SIEM Query:

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

🔗 References

📤 Share & Export