CVE-2025-47061

5.4 MEDIUM

📋 TL;DR

This stored XSS vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into form fields. When users visit pages containing the compromised fields, their browsers execute the attacker's code. Organizations running AEM versions 6.5.22 or earlier are affected.

💻 Affected Systems

Products:
  • Adobe Experience Manager
Versions: 6.5.22 and earlier
Operating Systems: All platforms running AEM
Default Config Vulnerable: ⚠️ Yes
Notes: Requires attacker to have low-privileged access to create/edit content with 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 full system compromise.

🟠

Likely Case

Attackers with low privileges steal session cookies or user data from other users who view the compromised pages.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts are neutralized before reaching user browsers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated low-privileged access to inject scripts into vulnerable form fields.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.5.23 or later

Vendor Advisory: https://helpx.adobe.com/security/products/experience-manager/apsb25-48.html

Restart Required: Yes

Instructions:

1. Download AEM 6.5.23 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

Input Validation Filter

all

Implement server-side input validation to sanitize user input in form fields

Configure AEM's XSS protection filters via OSGi console

Content Security Policy

all

Implement CSP headers to restrict script execution

Add 'Content-Security-Policy' header to AEM dispatcher configuration

🧯 If You Can't Patch

  • Restrict low-privileged user access to content creation/editing capabilities
  • Implement web application firewall rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check AEM version via CRXDE Lite or OSGi console - if version is 6.5.22 or earlier, system is vulnerable.

Check Version:

curl -u admin:password http://localhost:4502/system/console/status-productinfo.json | grep 'Adobe Experience Manager'

Verify Fix Applied:

After patching, verify version is 6.5.23 or later and test form fields with XSS payloads to ensure they're properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual content creation/modification by low-privileged users
  • Requests containing script tags or JavaScript in form submissions

Network Indicators:

  • HTTP requests with suspicious script payloads in POST parameters

SIEM Query:

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

🔗 References

📤 Share & Export