CVE-2024-26068

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 the compromised fields, their browsers execute the attacker's scripts. 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 supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both AEM Forms and AEM Sites implementations. Requires attacker access to vulnerable form fields.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, hijack user sessions, deface websites, or redirect users to malicious sites, potentially leading to complete system compromise.

🟠

Likely Case

Attackers steal user session cookies or credentials, perform actions on behalf of authenticated users, or conduct phishing attacks.

🟢

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 access or social engineering.

🛠️ 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 installation guide. 3. Restart the AEM instance. 4. Verify the update was successful.

🔧 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 header to restrict script execution sources.

🧯 If You Can't Patch

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

🔍 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:

Check AEM Welcome screen or use curl: curl -k https://<aem-host>:<port>/system/console/status-productinfo

Verify Fix Applied:

Verify 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
  • Requests containing JavaScript payloads in form parameters

Network Indicators:

  • HTTP requests with script tags in POST data
  • Unusual content-type submissions to form endpoints

SIEM Query:

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

🔗 References

📤 Share & Export