CVE-2024-36196

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.20 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where attackers can inject malicious JavaScript into vulnerable form fields. When users visit pages containing these compromised fields, their browsers execute the malicious scripts, potentially leading to session hijacking, data theft, or unauthorized actions.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both author and publish instances. Requires attacker access to vulnerable form fields, which may be limited by permissions.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, gain administrative access to the AEM instance, deface websites, install backdoors, or redirect users to malicious sites.

🟠

Likely Case

Attackers steal user session cookies or credentials, perform actions on behalf of authenticated users, or deface public-facing web pages.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires the attacker to have access to vulnerable form fields, which typically requires some level of authenticated access. The technical complexity of XSS injection is low.

🛠️ 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 the latest AEM 6.5 service pack from Adobe's distribution portal. 2. Apply the service pack following Adobe's installation instructions. 3. Restart the AEM instance. 4. Verify the update was successful.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

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

Content Security Policy

all

Implement a strict Content Security Policy (CSP) to mitigate the impact of XSS attacks by restricting script execution.

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads in form submissions.
  • Restrict access to vulnerable form fields using AEM permissions and disable unnecessary form components.

🔍 How to Verify

Check if Vulnerable:

Check AEM version via the welcome screen or system console. If version is 6.5.20 or earlier, the system is vulnerable.

Check Version:

Check the AEM welcome page at /libs/granite/core/content/login.html or use the system console at /system/console/status-productinfo

Verify Fix Applied:

After patching, verify the AEM version is 6.5.21 or later and test form fields for XSS vulnerabilities using security testing tools.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript code in request parameters
  • Multiple failed XSS attempts in access logs

Network Indicators:

  • HTTP requests containing script tags or JavaScript in form field parameters
  • Unusual outbound connections from user browsers after visiting AEM pages

SIEM Query:

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

🔗 References

📤 Share & Export