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-46895 Overview
Adobe Experience Manager (AEM) versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability [CWE-79]. A low-privileged attacker can inject malicious JavaScript into vulnerable form fields. The payload executes in a victim's browser when they view the page containing the affected field. Adobe published the fix in security bulletin APSB25-48. The vulnerability affects both on-premises AEM deployments and AEM Cloud Service.
Critical Impact
Authenticated attackers with low privileges can store malicious JavaScript that executes in victims' browsers, enabling session theft, credential harvesting, and actions performed in the victim's security context.
Affected Products
- Adobe Experience Manager 6.5.22 and earlier (on-premises)
- Adobe Experience Manager Cloud Service (affected releases per APSB25-48)
- AEM Forms component containing the vulnerable form field handling
Discovery Timeline
- 2025-06-10 - CVE-2025-46895 published to the National Vulnerability Database
- 2025-06-10 - Adobe published security bulletin APSB25-48
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-46895
Vulnerability Analysis
The vulnerability is a stored XSS flaw in Adobe Experience Manager form field handling. AEM fails to properly sanitize user-supplied input before persisting it and rendering it back to users. Attacker-supplied JavaScript is stored server-side and served as part of the page HTML. When a victim loads the affected page, the browser parses the injected script in the application's origin.
Exploitation requires authentication, so an attacker must hold a valid low-privileged account on the target AEM instance. User interaction is required: a victim must browse to the page containing the malicious field. Because the attack crosses a privilege boundary (scope change), a low-privileged author can impact higher-privileged users such as content reviewers or administrators who view the affected content.
The EPSS score is 0.328%, indicating low observed exploitation activity in the wild at this time.
Root Cause
The root cause is insufficient output encoding and input validation in AEM form field rendering. AEM accepts attacker-controlled markup in form field properties and emits it into the DOM without neutralizing active script content. This is a classic failure to apply contextual output encoding when rendering stored content, categorized under CWE-79.
Attack Vector
The attack vector is network-based through the AEM authoring or publishing interface. An authenticated attacker with content-editing privileges submits a payload into a vulnerable form field. The payload is persisted in the AEM repository. Any user who later renders the page executes the injected script. Typical payloads leverage <script> tags, event handlers such as onerror or onload, or javascript: URIs embedded in field attributes.
See the Adobe Security Bulletin APSB25-48 for vendor technical details.
Detection Methods for CVE-2025-46895
Indicators of Compromise
- Form field values in the AEM JCR repository containing <script>, javascript:, or inline event handlers such as onerror= and onload=
- Unexpected outbound HTTP requests from browsers rendering AEM pages to attacker-controlled domains
- Author account activity creating or modifying form components outside normal content workflows
Detection Strategies
- Review AEM audit logs for form component modifications performed by low-privileged author accounts
- Scan the JCR repository for stored content containing HTML or JavaScript tokens in fields intended to hold plain text
- Deploy a Content Security Policy (CSP) in report-only mode to surface inline script execution on rendered pages
Monitoring Recommendations
- Monitor web server access logs for anomalous POST requests to /content/forms/ and AEM authoring endpoints
- Alert on administrator or reviewer sessions loading pages immediately after low-privileged author modifications
- Track browser-side CSP violation reports from AEM-published sites for signs of injected inline script
How to Mitigate CVE-2025-46895
Immediate Actions Required
- Apply the Adobe security update referenced in APSB25-48 to AEM 6.5 installations
- Verify AEM Cloud Service instances are updated to a release that includes the fix
- Audit form components created or modified before patching for stored script payloads and remove any malicious content
- Review and tighten author-group permissions so only trusted roles can modify form fields
Patch Information
Adobe addressed the vulnerability in AEM 6.5.23 (Service Pack succeeding 6.5.22) and in the corresponding AEM Cloud Service release. Patch details and download instructions are documented in Adobe Security Bulletin APSB25-48.
Workarounds
- Enforce a strict Content Security Policy on AEM-published sites to block inline script execution
- Restrict form component authoring permissions to a minimal set of vetted author accounts
- Deploy a web application firewall rule to inspect form field submissions for script tags and dangerous event handlers
- Require secondary review of form component changes before promotion to publish instances
# Example restrictive Content Security Policy header for AEM Dispatcher
# Add to the Dispatcher or front-end web server configuration
Header always set Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'"
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

