CVE-2025-47044

5.4 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 scripts that execute in victims' browsers when they visit compromised pages. This affects all organizations running vulnerable AEM instances.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both author and publish instances. Requires attacker to have at least low-privileged access to input forms.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, perform actions as authenticated users, deface websites, or redirect users to malicious sites.

🟠

Likely Case

Attackers with low privileges could escalate privileges, steal user data, or perform limited malicious actions within the application context.

🟢

If Mitigated

With proper input validation and output encoding, the vulnerability would be prevented despite the underlying code flaw.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated access to vulnerable form fields. 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's distribution portal. 2. Apply the service pack following Adobe's upgrade documentation. 3. Restart all AEM instances. 4. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement custom servlet filters to sanitize form field inputs before processing

Implement Java servlet filter with OWASP Java Encoder library

Content Security Policy

all

Deploy strict CSP headers to mitigate script execution even if XSS occurs

Add 'Content-Security-Policy' header with script-src restrictions

🧯 If You Can't Patch

  • Restrict low-privileged user access to form creation and editing capabilities
  • Implement web application firewall rules to block XSS payload patterns

🔍 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. Test form fields with basic XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags
  • Multiple failed XSS attempts in request logs
  • Suspicious content creation by low-privileged users

Network Indicators:

  • HTTP requests containing script injection patterns
  • Unusual outbound connections from user browsers after visiting AEM pages

SIEM Query:

source="aem_logs" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export