CVE-2024-36141

5.4 MEDIUM

📋 TL;DR

This stored XSS vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing the compromised fields, their browsers execute the attacker's code. This affects AEM versions 6.5.20 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Requires low-privileged attacker access to vulnerable form fields.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, redirect users to malicious sites, perform actions on behalf of authenticated users, or deploy additional malware payloads.

🟠

Likely Case

Session hijacking, credential theft, or defacement of web pages through injected content.

🟢

If Mitigated

Limited impact with proper input validation, output encoding, and Content Security Policy (CSP) headers in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated low-privileged access to vulnerable form fields.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.21 or later

Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb24-28.html

Restart Required: Yes

Instructions:

1. Download AEM 6.5.21 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 update completed successfully.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources and prevent XSS payloads from running.

Add 'Content-Security-Policy' header with appropriate directives to web server configuration

Input Validation and Output Encoding

all

Implement server-side validation and proper output encoding for all user inputs in form fields.

Configure AEM's XSS protection filters and implement custom validation components

🧯 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 AEM version via the Welcome screen or CRX Package Manager. If version is 6.5.20 or earlier, the system is vulnerable.

Check Version:

Navigate to AEM Welcome screen or use 'curl http://localhost:4502/libs/granite/core/content/login.html | grep version'

Verify Fix Applied:

After patching, verify the version shows 6.5.21 or later and test form fields for XSS payload acceptance.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to form submission endpoints
  • Requests containing script tags or JavaScript payloads in parameters

Network Indicators:

  • HTTP requests with suspicious script content in form fields
  • Unexpected JavaScript execution in user sessions

SIEM Query:

source="aem_access.log" AND (method="POST" AND uri="/content/forms/af/*" AND (body="<script>" OR body="javascript:"))

🔗 References

📤 Share & Export