CVE-2025-46941

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 form fields. When users visit pages containing the compromised fields, their browsers execute the attacker's code. This affects AEM versions 6.5.22 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All supported platforms
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 session cookies, perform actions as authenticated users, or redirect users to malicious sites, potentially leading to full system compromise.

🟠

Likely Case

Attackers with low privileges steal session cookies or credentials from other users, escalate privileges, or deface website content.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts are neutralized before reaching user browsers, preventing 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 typically has low technical complexity once vulnerable fields are identified.

🛠️ 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 AEM 6.5.23 or later from Adobe distribution. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart all AEM instances. 4. Verify the update completed successfully.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement strict input validation and output encoding for all user-controllable form fields to neutralize malicious scripts.

Content Security Policy (CSP)

all

Deploy a strict Content Security Policy header to restrict script execution sources and mitigate XSS impact.

🧯 If You Can't Patch

  • Restrict low-privileged user access to form editing capabilities
  • Implement web application firewall (WAF) rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via OSGi console (http://host:port/system/console/bundles) or CRX Package Manager; versions 6.5.22 or earlier are vulnerable.

Check Version:

curl -s http://localhost:4502/system/console/bundles/org.apache.sling.installer.core | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify version shows 6.5.23 or later and test form fields with XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript code
  • Multiple failed XSS attempts in request 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