CVE-2024-26054

5.4 MEDIUM

📋 TL;DR

This stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows attackers to inject malicious JavaScript into vulnerable form fields. When users visit pages containing these compromised fields, their browsers execute the attacker's code. This affects Adobe Experience Manager versions 6.5.20 and earlier.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All platforms running Adobe Experience Manager
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both AEM Forms and AEM Sites components with vulnerable form fields.

📦 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 access to vulnerable forms could inject scripts that steal user session data or perform limited actions within the application context.

🟢

If Mitigated

With proper input validation and output encoding, the risk is reduced to minimal, though the vulnerability still exists in unpatched systems.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires access to vulnerable form fields, which typically requires some level of application access.

🛠️ 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 Adobe Experience Manager 6.5.21 or later from Adobe's distribution portal. 2. Follow Adobe's upgrade documentation for your deployment type (on-premise or cloud). 3. Apply the update to all affected instances. 4. Restart the AEM service.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and output encoding for all form fields to prevent script injection.

Content Security Policy

all

Implement a strict Content Security Policy (CSP) to mitigate the impact of successful XSS attacks.

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Restrict access to vulnerable form fields to trusted users only

🔍 How to Verify

Check if Vulnerable:

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

Check Version:

curl -k https://[aem-host]:[port]/system/console/status-productinfo | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify the version is 6.5.21 or later and test form fields for XSS vulnerabilities.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags or JavaScript code
  • Multiple failed validation attempts on form fields

Network Indicators:

  • HTTP requests containing script payloads in form parameters
  • Unusual outbound connections from user browsers after form submissions

SIEM Query:

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

🔗 References

📤 Share & Export