Skip to main content
Vulnerability Database/CVE-2025-47067

CVE-2025-47067: Adobe Experience Manager XSS Vulnerability

CVE-2025-47067 is a stored Cross-Site Scripting vulnerability in Adobe Experience Manager that allows low privileged attackers to inject malicious scripts. This article covers technical details, affected versions, and mitigation.

Published:

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-47067 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. When a victim visits the page rendering the affected field, the injected script executes in the victim's browser session.

The vulnerability affects both on-premises Adobe Experience Manager deployments and the AEM Cloud Service. Exploitation requires user interaction and low-level privileges, but the scope change allows the injected script to impact resources beyond the vulnerable component.

Critical Impact

Stored XSS enables session hijacking, credential theft, and unauthorized actions performed in the context of authenticated AEM users, including administrators who browse affected pages.

Affected Products

  • Adobe Experience Manager 6.5.22 and earlier (on-premises)
  • Adobe Experience Manager Cloud Service (affected versions prior to the APSB25-48 fix)
  • AEM form components that process unsanitized user-supplied content

Discovery Timeline

  • 2025-06-10 - CVE-2025-47067 published to the National Vulnerability Database
  • 2025-06-10 - Adobe publishes security bulletin APSB25-48
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-47067

Vulnerability Analysis

The flaw is a stored Cross-Site Scripting weakness classified under [CWE-79]: Improper Neutralization of Input During Web Page Generation. AEM form fields fail to properly sanitize or encode user-supplied input before storing it in the content repository and rendering it in HTML output.

Because the payload is persisted, every subsequent visitor to the affected page receives the attacker's script. The scope change in this vulnerability indicates that script execution reaches a security authority different from the vulnerable component, extending impact beyond the form itself.

Exploitation requires a low-privileged authenticated account with permission to submit content into vulnerable form fields. Victim interaction is also required because the script executes only when a user loads the affected page.

Root Cause

AEM accepts user input into form fields without applying context-aware output encoding or input neutralization. The stored payload is later reflected into the Document Object Model (DOM) as executable HTML or JavaScript, rather than inert text. This failure to encode HTML metacharacters such as <, >, and " on output allows arbitrary script injection.

Attack Vector

An attacker authenticates to AEM with a low-privileged account, such as a content contributor. The attacker submits a crafted payload containing JavaScript into a vulnerable form field. The payload is persisted in the AEM repository.

When another authenticated user, including an administrator, navigates to the page displaying the field, the browser parses and executes the injected script. The script runs with the victim's session context and can exfiltrate authentication cookies, perform actions on behalf of the victim, or pivot to other AEM functionality. See the Adobe Security Advisory APSB25-48 for product-specific technical details.

Detection Methods for CVE-2025-47067

Indicators of Compromise

  • Form field content containing HTML tags such as <script>, <img onerror=>, <svg onload=>, or JavaScript URI schemes
  • Unexpected outbound HTTP requests from authenticated AEM user sessions to attacker-controlled domains
  • AEM audit log entries showing content modifications to form fields by low-privileged accounts followed by access from higher-privileged users
  • Browser console errors or Content Security Policy violations originating from AEM-authored pages

Detection Strategies

  • Review AEM content repository entries for form field values containing script tags, event handlers, or encoded payloads
  • Enable and monitor AEM Dispatcher and request logs for anomalous POST payloads submitted to form submission endpoints
  • Deploy a Content Security Policy (CSP) in report-only mode to surface inline script execution attempts on AEM pages

Monitoring Recommendations

  • Alert on repeated form submissions from the same low-privileged account containing HTML or JavaScript metacharacters
  • Correlate form field modification events with subsequent administrator page views to identify potential victim exposure
  • Monitor for session cookie exfiltration patterns in web proxy and egress firewall logs

How to Mitigate CVE-2025-47067

Immediate Actions Required

  • Apply the Adobe security update referenced in APSB25-48 to all AEM 6.5.x and Cloud Service instances
  • Audit existing form field content for stored payloads containing HTML tags or JavaScript before patching
  • Review and restrict AEM group memberships to limit which accounts can submit content into form components

Patch Information

Adobe released fixes in security bulletin APSB25-48 on June 10, 2025. Upgrade on-premises AEM deployments to the version specified in the advisory. AEM Cloud Service customers receive updates through Adobe's managed release channel. Refer to the Adobe Security Advisory APSB25-48 for exact version numbers and installation procedures.

Workarounds

  • Enforce a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins
  • Place AEM behind a web application firewall configured to block script injection patterns in form POST bodies
  • Temporarily revoke write access to affected form components for low-privileged user groups until the patch is deployed
bash
# Example AEM Dispatcher filter rule to block script tags in POST bodies
/0100 { /type "deny" /method "POST" /url '*<script*' }
/0101 { /type "deny" /method "POST" /url '*javascript:*' }

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.