CVE-2024-26083

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.20 and earlier contain a stored cross-site scripting vulnerability in form fields. An attacker can inject malicious JavaScript that executes in victims' browsers when they view compromised pages. This affects all users of vulnerable Adobe Experience Manager instances.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All
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 session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware via drive-by downloads.

🟠

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 headers in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Requires attacker to have access to inject content into vulnerable form fields, typically through authenticated access or other entry points.

🛠️ 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. Apply the service pack following Adobe's upgrade documentation. 3. Restart the AEM instance. 4. Verify the update was successful.

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add Content Security Policy headers to restrict script execution from untrusted sources.

Add 'Content-Security-Policy: script-src 'self'' to HTTP headers

Input Validation Filter

all

Implement server-side input validation to sanitize form field inputs.

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

🧯 If You Can't Patch

  • Restrict user permissions to minimize who can submit content to vulnerable form fields.
  • Implement web application firewall rules to block XSS payload patterns.

🔍 How to Verify

Check if Vulnerable:

Check AEM version via the welcome page or OSGi console. Versions 6.5.20 and earlier are vulnerable.

Check Version:

Check /system/console/bundles for org.apache.sling.servlets.get version or visit /libs/granite/core/content/login.html welcome page

Verify Fix Applied:

Verify AEM version is 6.5.21 or later and test form fields with XSS payloads to ensure they're properly sanitized.

📡 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 parameters
  • Unexpected outbound connections from client browsers after visiting AEM pages

SIEM Query:

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

🔗 References

📤 Share & Export