Sigma · CVE exploitation
IIS / ASP.NET stack: IIS worker process spawned a shell or LOLBin
- 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
title: 'Skopnix - IIS / ASP.NET stack: IIS worker process spawned a shell or LOLBin'id: 2d7018f1-74d9-54f0-916c-695ef1699035status: experimentaldescription: '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.'references: - https://skopnix.com/cve/CVE-2026-118151 - https://skopnix.com/cve/CVE-2026-118149 - https://skopnix.com/cve/CVE-2026-106931 - https://skopnix.com/cve/CVE-2026-65660 - https://skopnix.com/cve/CVE-2025-53771 - https://skopnix.com/cve/CVE-2025-53770 - https://skopnix.com/cve/CVE-2019-18935author: skopnixdate: '2026-11-14'tags: - attack.execution - attack.t1190 - attack.t1505.003 - attack.t1059.001 - attack.t1059.003 - cve.2026-118151 - cve.2026-118149 - cve.2026-106931 - cve.2026-65660 - cve.2025-53771 - cve.2025-53770 - cve.2019-18935logsource: category: process_creation product: windowsdetection: selection_parent: ParentImage|endswith: \w3wp.exe selection_child: Image|endswith: - \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 condition: selection_parent and selection_childfalsepositives: - Line-of-business applications that shell out from ASP.NET by design (baseline by application pool and command line)level: highskopnix-sigma-cve-stack-iis-dotnet-w3wp-shell-ed7aed65.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.