CVE-2025-46920

4.6 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.22 and earlier contain a stored cross-site scripting vulnerability in form fields. Low-privileged attackers can inject malicious JavaScript that executes in victims' browsers when they visit compromised pages. This affects all organizations using vulnerable AEM versions.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged user 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 administrator session cookies, perform actions as authenticated users, or redirect users to malicious sites, potentially leading to full system compromise.

🟠

Likely Case

Low-privileged users could escalate privileges, steal session data from other users, or deface website content through injected scripts.

🟢

If Mitigated

With proper input validation and output encoding, the risk is limited to potential data leakage from users who interact with malicious content.

🌐 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 means payload persists until cleaned.

🛠️ 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. Backup current instance. 3. Apply service pack following Adobe's upgrade documentation. 4. Restart AEM instance. 5. Verify successful upgrade.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filter to sanitize form field inputs

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

Content Security Policy

all

Implement strict CSP headers to mitigate script execution

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

🧯 If You Can't Patch

  • Restrict low-privileged user access to vulnerable form fields
  • Implement web application firewall with XSS protection rules

🔍 How to Verify

Check if Vulnerable:

Check AEM version via CRXDE Lite or system console. If version is 6.5.22 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.23 or later and test form fields with XSS payloads.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form endpoints
  • JavaScript payloads in request parameters
  • Multiple failed XSS attempts

Network Indicators:

  • Suspicious script tags in HTTP POST data
  • Unusual outbound connections from AEM server

SIEM Query:

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

🔗 References

📤 Share & Export