CVE-2025-46861

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting vulnerability that 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, potentially leading to session hijacking or data theft.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all deployment types (on-premise, cloud, hybrid). Low-privileged users can exploit this vulnerability.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator sessions, compromise user accounts, deface websites, or redirect users to malicious sites, potentially leading to full system compromise.

🟠

Likely Case

Low-privileged attackers inject malicious scripts to steal session cookies or user credentials from other users accessing the affected pages.

🟢

If Mitigated

With proper input validation and output encoding, the impact is limited to minor data exposure or temporary service disruption.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Requires authenticated low-privileged access. Exploitation involves injecting JavaScript into vulnerable form fields.

🛠️ 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 distribution portal. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart the AEM instance. 4. Verify the patch is applied correctly.

🔧 Temporary Workarounds

Input Validation Filter

all

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

Configure AEM's XSS protection filters in /system/console/configMgr

Content Security Policy

all

Implement strict CSP headers to restrict script execution

Add Content-Security-Policy headers via Apache/Dispatcher 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.22 or earlier, the system is vulnerable.

Check Version:

curl -u admin:password http://localhost:4502/system/console/status-productinfo.json | grep version

Verify Fix Applied:

After patching, verify version is 6.5.23 or later and test form fields for XSS by attempting to inject basic script payloads.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content modifications by low-privileged users
  • JavaScript payloads in request logs
  • Multiple failed XSS attempts

Network Indicators:

  • Unexpected script tags in HTTP responses
  • Suspicious content in form submissions

SIEM Query:

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

🔗 References

📤 Share & Export