Cortex XDR · CVE exploitation
IIS / ASP.NET stack: IIS worker process spawned a shell or LOLBin
- Correlation
- set the rule's MITRE tactic to TA0002 and technique to T1505.003
- severity
- high
- confidence
- 75/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2019-18935 · CVE-2025-53770 · CVE-2025-53771 · CVE-2026-106931 · CVE-2026-118149 · CVE-2026-118151 · CVE-2026-65660
w3wp.exe started cmd, PowerShell, a script host or a download / proxy-execution LOLBin. Web shells and RCE in IIS-hosted applications run their commands this way. Not specific to one bug: it fires on code execution through the IIS / ASP.NET stack by any route. Attached to the 7 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-118151, CVE-2026-118149, CVE-2026-106931.
False-positive notes
Needs w3wp.exe as the PARENT and one of cmd, PowerShell, pwsh, wscript, cscript, mshta, rundll32, regsvr32, certutil, bitsadmin, whoami, net, nltest or curl as the child. The compiler (csc.exe, vbc.exe) and conhost are not in the list, so ASP.NET page compilation does not match. Applications that call cmd by design will: baseline by app pool first.
References
dataset = xdr_data| filter event_type = ENUM.PROCESS and event_sub_type = ENUM.PROCESS_START| filter lowercase(actor_process_image_name) = "w3wp.exe" and lowercase(action_process_image_name) in ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "certutil.exe", "bitsadmin.exe", "whoami.exe", "net.exe", "net1.exe", "nltest.exe", "curl.exe")| fields _time, agent_hostname, actor_effective_username, action_process_image_name, action_process_image_command_line, actor_process_image_name, causality_actor_process_image_name| sort desc _timeskopnix-cortex-cve-stack-iis-dotnet-w3wp-shell-dfe86350.xql
How to deploy on Cortex XDR
- Step 1
- Paste the XQL into Incident Response > Investigation > Query Builder > XQL Search.
- Step 2
- To alert, save it as a Correlation Rule and set the MITRE tactic and technique printed with the rule.
- Step 3
- Schedule it on the interval you hunt at; keep the fields stage for the alert's columns.
- Check
- CVE rules read PAN-OS URL logs (panw_ngfw_url_raw), which need the NGFW integration and, for HTTPS, decryption.