CVE-2024-26071

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 visit compromised pages. This affects all users of vulnerable AEM instances.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.20 and earlier
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both author and publish instances. Requires attacker to have access to 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

Exploitation requires ability to submit data to vulnerable form fields. May require some authentication depending on field accessibility.

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

🔧 Temporary Workarounds

Implement Content Security Policy

all

Add CSP headers to restrict script execution from untrusted sources

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

Input Validation Filter

all

Implement server-side input validation for all form fields

Configure AEM filters to sanitize user input before processing

🧯 If You Can't Patch

  • Restrict access to vulnerable form fields using AEM permissions
  • Implement web application firewall rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via CRXDE Lite or system console. If version is 6.5.20 or earlier, system is vulnerable.

Check Version:

curl -u admin:password http://localhost:4502/system/console/status-productinfo

Verify Fix Applied:

Verify AEM version is 6.5.21 or later and test form fields for XSS payload acceptance.

📡 Detection & Monitoring

Log Indicators:

  • Unusual form submissions with script tags
  • Requests containing JavaScript payloads in parameters

Network Indicators:

  • HTTP requests with suspicious script content in POST data

SIEM Query:

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

🔗 References

📤 Share & Export