CVE-2024-43751

5.4 MEDIUM

📋 TL;DR

Adobe Experience Manager versions 6.5.21 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 pages with the vulnerable fields. This affects all users of vulnerable Adobe Experience Manager instances.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.21 and earlier
Operating Systems: All platforms running Adobe Experience Manager
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both author and publish instances. Vulnerability exists in form fields that don't properly sanitize user input.

📦 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 through drive-by downloads.

🟠

Likely Case

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

🟢

If Mitigated

Limited impact if proper input validation and output encoding are implemented, though stored XSS remains dangerous.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires ability to submit content to vulnerable form fields, which typically requires some level of access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.22 or later

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

Restart Required: Yes

Instructions:

1. Download Adobe Experience Manager 6.5.22 or later 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 Filter

all

Implement custom servlet filters to sanitize form field input before processing.

Implement Java servlet filter with input validation logic for form parameters

Content Security Policy

all

Implement strict CSP headers to mitigate XSS impact.

Add 'Content-Security-Policy' header with script-src directives

🧯 If You Can't Patch

  • Implement web application firewall rules to block XSS payloads in form submissions
  • Disable or restrict access to vulnerable form fields through access controls

🔍 How to Verify

Check if Vulnerable:

Check Adobe Experience Manager version via AEM Web Console (/system/console) or by examining the CRX package manager.

Check Version:

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

Verify Fix Applied:

Verify version is 6.5.22 or later and test form fields with XSS payloads to confirm sanitization.

📡 Detection & Monitoring

Log Indicators:

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

Network Indicators:

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

SIEM Query:

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

🔗 References

📤 Share & Export