Adobe Experience Manager patches 100+ flaws
Adobe fixed over 100 vulnerabilities in Experience Manager, including a critical 9.9 authorization bug allowing code execution without interaction, plus widespread XSS issues.
NCSC-NL published an advisory summarizing a large batch of vulnerabilities patched by Adobe in Adobe Experience Manager (AEM). The bulk of the issues are Cross-Site Scripting (XSS) flaws, both DOM-based and stored, stemming from insufficient input sanitization and output encoding in form components. These allow an attacker to inject and execute malicious JavaScript in the browser of a user who visits or interacts with a crafted page, potentially leading to unauthorized actions in the context of the victim's session.
Of particular note is CVE-2026-19232 (CVSS 9.9), an Incorrect Authorization vulnerability that allows a low-privileged attacker to execute arbitrary code without any user interaction due to improper authorization checks within the application. CVE-2026-27238 (CVSS 7.8) is also notably higher severity than the rest of the batch. An additional Improper Input Validation issue allows security control bypass and acquisition of restricted write permissions via malicious URLs or webpages. No evidence of active exploitation in the wild is mentioned in this advisory; it is a routine vendor patch release.
Defenders running Adobe Experience Manager should apply the vendor updates referenced in the advisory as soon as feasible, prioritizing patching for CVE-2026-19232 given its severity and lack of required user interaction. Organizations should also review AEM instances for exposure to form components handling untrusted input, and monitor for anomalous authorization or session activity consistent with XSS or authorization-bypass exploitation attempts.
Mentioned in this report
Detection guidance
Suspicious JavaScript Execution from AEM Form Components
Detects JavaScript execution in browser context originating from Adobe Experience Manager form component responses, indicative of XSS payload delivery. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Suspicious JavaScript Execution from AEM Form Components
description: Detects JavaScript code execution initiated by HTTP responses from AEM
form component endpoints, which may indicate stored or DOM-based XSS exploitation.
Monitors for anomalous script execution patterns following requests to known AEM
form handling paths.
tags:
- attack.execution
- attack.t1059.007
logsource:
category: proxy
product: windows
detection:
selection:
DestinationHostname|contains:
- /forms/
- /content/forms/
http_method: GET|POST
response_code: '200'
http_response_body|contains:
- <script
- 'javascript:'
- onerror=
- onload=
- onclick=
filter_legitimate_form_response:
http_response_body|contains:
- Content-Security-Policy
- 'X-Content-Type-Options: nosniff'
condition: selection and not filter_legitimate_form_response
falsepositives:
- Legitimate AEM form components with embedded client-side validation scripts
- Developer testing environments with unencoded form responses
level: medium
id: 6f70411e-9a4d-5dbe-8aff-a06f0753a1b7
status: experimental
author: Vorant
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0363.html
This is the public brief
Subscribers see the full picture: extracted IOCs, ready-to-deploy detections (Sigma, Splunk, KQL, Elastic, YARA, Suricata), the entity graph, TAXII 2.1 feed and real-time alerts matched to your sectors.
Start free