Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-46950 Overview
Adobe Experience Manager (AEM) versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability [CWE-79]. A low-privileged authenticated attacker can inject malicious JavaScript into vulnerable form fields. The payload executes in a victim's browser when the user loads the page rendering the affected field. The flaw affects both on-premises AEM deployments and AEM Cloud Service. Adobe addressed the issue in Security Advisory APSB25-48.
Critical Impact
Authenticated attackers can plant persistent JavaScript payloads in AEM form fields, enabling session theft, content tampering, and client-side actions executed under the victim's authority.
Affected Products
- Adobe Experience Manager 6.5.22 and earlier (on-premises)
- Adobe Experience Manager Cloud Service (affected release channel)
- AEM Forms components rendering unsanitized field input
Discovery Timeline
- 2025-06-10 - CVE-2025-46950 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-46950
Vulnerability Analysis
The vulnerability is a stored XSS flaw in AEM form field handling. Content authored by a low-privileged user is persisted without adequate output encoding. When another user, including higher-privileged administrators, renders the containing page, the stored payload executes in the browser context of the AEM origin.
Because the attack requires authenticated input and victim interaction, it falls short of a direct remote code execution class. However, scope-changing execution against administrative sessions can lead to privileged content manipulation, workflow abuse, and lateral movement within the AEM authoring environment.
Root Cause
The root cause is improper neutralization of user-supplied input during web page generation [CWE-79]. Form field values submitted by an authenticated user are stored in the repository and later emitted to HTML without context-appropriate escaping, allowing <script> or event-handler payloads to render as executable markup.
Attack Vector
An attacker with a low-privileged AEM account submits crafted input to a form field exposed through the authoring or publish surface. The payload persists in the Java Content Repository (JCR). When a victim navigates to the page containing the field, the browser parses the injected script and runs it under the AEM domain. The attacker can exfiltrate session cookies, issue authenticated API calls on behalf of the victim, or deface rendered pages.
No verified public exploit or proof-of-concept is available at the time of writing. Refer to the Adobe Security Advisory APSB25-48 for vendor-provided technical details.
Detection Methods for CVE-2025-46950
Indicators of Compromise
- Form field values in the JCR containing HTML tags, <script> elements, or on* event handler attributes
- Unexpected outbound requests from authoring or publish instances to attacker-controlled domains following page loads
- AEM access logs showing form submissions from low-privileged accounts followed by administrator visits to the same resource paths
Detection Strategies
- Query the JCR for recently modified nodes containing suspicious character sequences such as <script, javascript:, onerror=, or onload= in form-related properties
- Enable Content Security Policy (CSP) reporting on AEM-rendered pages to surface inline script execution attempts
- Review AEM audit logs for form field edits by non-administrative accounts targeting pages consumed by privileged users
Monitoring Recommendations
- Alert on anomalous dispatcher or publish responses containing user-controlled strings reflected into HTML without encoding
- Monitor administrator sessions for unexpected XHR or fetch activity originating from page views, which may indicate stored payload execution
- Correlate account creation, form submissions, and subsequent privileged logins across AEM authoring instances
How to Mitigate CVE-2025-46950
Immediate Actions Required
- Upgrade on-premises AEM to the fixed service pack listed in Adobe Security Advisory APSB25-48
- Ensure AEM Cloud Service instances are running the latest release containing the fix
- Audit low-privileged accounts with form authoring permissions and remove unused access
- Review existing form field content for previously injected payloads and sanitize affected nodes
Patch Information
Adobe released fixes for Adobe Experience Manager addressing this vulnerability as part of Security Advisory APSB25-48. Administrators should apply the latest AEM 6.5 service pack above 6.5.22 and confirm AEM as a Cloud Service is on a release that includes the fix. See the Adobe Security Advisory APSB25-48 for version-specific guidance.
Workarounds
- Restrict form authoring permissions to trusted users until the patch is applied
- Deploy a strict Content Security Policy that disallows inline scripts on AEM-rendered pages
- Configure the AEM Dispatcher to filter or reject request payloads containing HTML control characters in form field parameters
- Apply server-side output encoding in custom components that render form field values
# Example Dispatcher filter snippet to block script-like payloads in form parameters
/0100 { /type "deny" /glob "*<script*" }
/0101 { /type "deny" /glob "*javascript:*" }
/0102 { /type "deny" /glob "*onerror=*" }
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

