CVE-2025-47115

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.22 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All platforms running Adobe Experience Manager
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 session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware through drive-by downloads.

🟠

Likely Case

Session hijacking, credential theft, defacement of web pages, or limited data exfiltration from user sessions.

🟢

If Mitigated

Minimal impact if proper input validation and output encoding are implemented, though some functionality disruption may occur.

🌐 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. No public exploit code is currently available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.23 or later

Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb25-48.html

Restart Required: Yes

Instructions:

1. Download Adobe Experience Manager 6.5.23 or later from Adobe's official distribution. 2. Follow Adobe's upgrade documentation for your deployment type. 3. Apply the update to all affected instances. 4. Restart the AEM service.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and proper output encoding for all user-controllable form fields.

Content Security Policy (CSP)

all

Implement a strict Content Security Policy to restrict script execution sources.

🧯 If You Can't Patch

  • Restrict low-privileged user access to vulnerable form fields and components.
  • Implement web application firewall (WAF) rules to detect and block XSS payloads.

🔍 How to Verify

Check if Vulnerable:

Check Adobe Experience Manager version via AEM Web Console (/system/console) or by examining the AEM installation directory.

Check Version:

Check via AEM Web Console at /system/console or examine crx-quickstart/logs/error.log for version information.

Verify Fix Applied:

Verify the version is 6.5.23 or later and test form fields with XSS payloads to ensure they are properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript payloads
  • Multiple failed XSS attempts in access logs

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form parameters
  • Unexpected outbound connections from user browsers

SIEM Query:

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

🔗 References

📤 Share & Export