A critical vulnerability in Optimizely CMS (formerly Episerver) is being actively exploited in the wild to serve malware through some of the highest-traffic websites on the internet. Confirmed victims include BBC, CNN, Zoom, GitLab, Salesforce, Equifax, HSBC, and IKEA — organizations whose web properties collectively handle hundreds of millions of sessions per month. This is not a theoretical risk. Attackers have already demonstrated the ability to weaponize compromised Optimizely instances as malware delivery infrastructure, turning trusted brand domains into watering-hole distribution points.
For defenders, this incident represents a worst-case scenario in third-party platform risk: a single unpatched CMS component converting your public-facing web presence into an attack vector against your own customers. The reputational and regulatory exposure — particularly for financial services and healthcare organizations subject to PCI-DSS and HIPAA — is severe. If your organization runs Optimizely CMS in any capacity, treat this as an immediate priority-one remediation event.
Technical Analysis
Affected Platform
Optimizely CMS is a .NET-based enterprise content management platform running primarily on Windows Server with IIS. It is deployed extensively across media, financial services, retail, and SaaS organizations — exactly the verticals represented in the confirmed victim list. Organizations running Optimizely in on-premises or IaaS-hosted configurations are directly exposed. Organizations using Optimizely's fully managed SaaS offering should confirm with the vendor that their tenant has been patched, but the primary risk concentrates on self-managed deployments where patching is the customer's responsibility.
Attack Chain
Based on the observed exploitation pattern, the attack chain proceeds as follows:
- Initial access via CMS vulnerability — The attacker exploits the Optimizely flaw to achieve unauthorized write access or code execution within the CMS application context. This does not require prior authentication in the observed campaigns.
- Web shell or malicious payload deployment — Post-exploitation, attackers drop persistent access mechanisms into the CMS web root or media/upload directories. ASPX web shells are the most common artifact in IIS-based CMS compromises of this type.
- Malware injection into served content — The compromised CMS is then used to inject malicious JavaScript or redirect logic into legitimate pages, serving malware to site visitors. Because the content is delivered from the organization's own legitimate domain, it inherits the site's trust, bypasses domain-reputation controls, and evades most user suspicion.
This technique maps to MITRE ATT&CK T1190 (Exploit Public-Facing Application) for initial access, T1505.003 (Web Shell) for persistence, and T1189 (Drive-by Compromise) for downstream victim infection.
Exploitation Status
Active, confirmed in-the-wild exploitation against major production websites. This is not a proof-of-concept or simulated exercise — the victim list published in the SecurityWeek reporting reflects real compromises. Organizations should assume scanning and exploitation attempts are ongoing and will accelerate now that public reporting has drawn attention to the flaw.
Detection & Response
The detections below target the observable post-exploitation behaviors of this campaign: web shell deployment in IIS/Optimizely paths, suspicious child processes spawned by the IIS worker process, and anomalous outbound connections from web server processes. Tune path filters to your actual Optimizely installation root.
---
title: IIS Worker Process Spawning Suspicious Child Process — Optimizely CMS Exploitation
id: 8f2a1b3c-4d5e-6f70-8192-a3b4c5d6e7f8
status: experimental
description: Detects w3wp.exe spawning cmd, powershell, or other command interpreters — a strong indicator of web shell activity following CMS exploitation on IIS-hosted platforms such as Optimizely.
references:
- https://attack.mitre.org/techniques/T1505/003/
- https://attack.mitre.org/techniques/T1190/
author: Security Arsenal
date: 2026/01/15
tags:
- attack.persistence
- attack.t1505.003
- attack.initial_access
- attack.t1190
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith: '\w3wp.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\cscript.exe'
- '\wscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\curl.exe'
- '\wget.exe'
condition: selection_parent and selection_child
falsepositives:
- Legitimate Optimizely add-ons or custom integrations that invoke scripts during content publishing workflows — baseline and exclude known-good parent/child pairs by CommandLine hash
level: high
---
title: ASPX Web Shell File Creation in Optimizely Web Root or Upload Directories
id: 3b7c9d1e-2f4a-5b6c-7d8e-9f0a1b2c3d4e
status: experimental
description: Detects creation of ASPX/ASHX/ASMX script files in Optimizely web root, media, or upload paths — consistent with web shell deployment following CMS exploitation.
references:
- https://attack.mitre.org/techniques/T1505/003/
author: Security Arsenal
date: 2026/01/15
tags:
- attack.persistence
- attack.t1505.003
logsource:
category: file_event
product: windows
detection:
selection_extension:
TargetFilename|endswith:
- '.aspx'
- '.ashx'
- '.asmx'
- '.ascx'
- '.cshtml'
selection_path:
TargetFilename|contains:
- '\inetpub\wwwroot\'
- '\optimizely\'
- '\episerver\'
- '\uploads\'
- '\media\'
- '\appdata\'
- '\modules\'
- '\util\'
filter_known_deploy:
Image|endswith:
- '\w3wp.exe'
- '\deploy.exe'
condition: selection_extension and selection_path and not filter_known_deploy
falsepositives:
- Legitimate CMS deployments and content publishing — correlate with deployment windows and CI/CD pipeline activity; alert on any creation outside of a known change window
level: high
---
title: Suspicious Outbound Network Connection from IIS Worker Process
id: 5e1f2a3b-4c5d-6e7f-8091-a2b3c4d5e6f7
status: experimental
description: Detects w3wp.exe initiating outbound connections to non-standard ports or external IPs — indicative of web shell callback, payload retrieval, or C2 activity following CMS compromise.
references:
- https://attack.mitre.org/techniques/T1071/
- https://attack.mitre.org/techniques/T1105/
author: Security Arsenal
date: 2026/01/15
tags:
- attack.command_and_control
- attack.t1071
- attack.exfiltration
logsource:
category: network_connection
product: windows
detection:
selection:
Image|endswith: '\w3wp.exe'
Initiated: 'true'
filter_standard:
DestinationPort:
- 80
- 443
condition: selection and not filter_standard
falsepositives:
- Database connections (1433, 1521), API integrations, and monitoring agents — build a destination allowlist for your environment and alert on deviations
level: medium
// Hunt for web shell indicators on IIS servers hosting Optimizely CMS
// Requires: MDE (DeviceProcessEvents / DeviceNetworkEvents) or Sysmon via Sentinel
let suspiciousInterpreters = dynamic(["cmd.exe", "powershell.exe", "pwsh.exe", "cscript.exe", "wscript.exe", "mshta.exe", "rundll32.exe", "certutil.exe", "bitsadmin.exe", "curl.exe", "wget.exe"]);
// 1. IIS worker process spawning command interpreters
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where InitiatingProcessFileName =~ "w3wp.exe"
| where FileName in~ (suspiciousInterpreters)
| project TimeGenerated, DeviceName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName, InitiatingProcessParentFileName
| order by TimeGenerated desc
;
// 2. Script file creation in web-served directories
DeviceFileEvents
| where TimeGenerated > ago(14d)
| where FileName endswith ".aspx" or FileName endswith ".ashx" or FileName endswith ".asmx" or FileName endswith ".cshtml"
| where FolderPath has_any ("\\inetpub\\", "\\optimizely\\", "\\episerver\\", "\\uploads\\", "\\media\\", "\\modules\\")
| where ActionType == "FileCreated"
| project TimeGenerated, DeviceName, FolderPath, FileName, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA256
| order by TimeGenerated desc
;
// 3. Outbound connections from w3wp.exe on non-standard ports
DeviceNetworkEvents
| where TimeGenerated > ago(14d)
| where InitiatingProcessFileName =~ "w3wp.exe"
| where RemotePort !in (80, 443, 1433)
| where RemoteIPType == "Public"
| summarize ConnectionCount = count(), DistinctPorts = make_set(RemotePort) by DeviceName, RemoteIP, RemoteUrl, InitiatingProcessCommandLine
| order by ConnectionCount desc
-- Velociraptor hunt: Web shell artifacts and suspicious IIS child processes on Optimizely hosts
-- Deploy as a hunt across all Windows servers running IIS/Optimizely
-- 1. Enumerate suspicious child processes of w3wp.exe
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime,
pslist(pid=Ppid)[0].Name AS ParentName,
pslist(pid=Ppid)[0].Exe AS ParentExe
FROM pslist()
WHERE ParentExe =~ '(?i)w3wp\.exe$'
AND Name =~ '(?i)cmd|powershell|pwsh|cscript|wscript|mshta|rundll32|certutil|bitsadmin|curl|wget'
-- 2. Find recently created script files in web root and upload directories
SELECT FullPath, Size, Mtime, Ctime, Atime, Mode
FROM glob(globs=[
'C:/inetpub/**/*.aspx',
'C:/inetpub/**/*.ashx',
'C:/inetpub/**/*.asmx',
'D:/inetpub/**/*.aspx',
'D:/inetpub/**/*.ashx',
'C:/**/uploads/*.aspx',
'C:/**/media/*.aspx',
'C:/**/modules/*.aspx'
])
WHERE Mtime > now() - 1209600
ORDER BY Mtime DESC
-- 3. Active network connections from IIS worker processes
SELECT Pid, Name, LocalAddr, LocalPort, RemoteAddr, RemotePort, State
FROM netstat()
WHERE Name =~ '(?i)w3wp'
AND RemotePort NOT IN (80, 443, 1433)
AND State =~ 'ESTABLISHED'
# Optimizely CMS Compromise Assessment and Hardening Script
# Run on each Windows Server hosting Optimizely CMS (elevated PowerShell)
# Author: Security Arsenal | Date: 2026-01-15
#Requires -RunAsAdministrator
$ErrorActionPreference = 'Continue'
$reportPath = "C:\OptimizelyAudit_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
"=== Optimizely CMS Security Assessment ===" | Out-File $reportPath
# --- 1. Identify Optimizely/Episerver installations and versions ---
"`n[1] Installed Optimizely/Episerver Components" | Out-File $reportPath -Append
$optiPaths = @("C:\inetpub\wwwroot", "D:\inetpub\wwwroot", "C:\EPiServer", "D:\EPiServer", "C:\Optimizely", "D:\Optimizely")
foreach ($p in $optiPaths) {
if (Test-Path $p) {
Get-ChildItem -Path $p -Recurse -Filter "EPiServer*.dll" -ErrorAction SilentlyContinue |
Select-Object FullName, @{N='Version';E={$_.VersionInfo.ProductVersion}} |
Out-File $reportPath -Append
}
}
Get-ChildItem -Path "C:\inetpub","D:\inetpub" -Recurse -Filter "Optimizely*.dll" -ErrorAction SilentlyContinue |
Select-Object FullName, @{N='Version';E={$_.VersionInfo.ProductVersion}} |
Out-File $reportPath -Append
# --- 2. Hunt for recently created web shell files in IIS-served paths ---
"`n[2] Recently Created Script Files (last 14 days) in Web Directories" | Out-File $reportPath -Append
$cutoff = (Get-Date).AddDays(-14)
$webExts = @('*.aspx','*.ashx','*.asmx','*.ascx','*.cshtml','*.php','*.jsp')
foreach ($ext in $webExts) {
Get-ChildItem -Path "C:\inetpub","D:\inetpub" -Recurse -Filter $ext -ErrorAction SilentlyContinue |
Where-Object { $_.CreationTime -gt $cutoff } |
Select-Object FullName, CreationTime, LastWriteTime, Length |
Out-File $reportPath -Append
}
# --- 3. Audit for suspicious child processes of w3wp.exe (via event logs) ---
"`n[3] Suspicious w3wp.exe Child Processes (last 14 days)" | Out-File $reportPath -Append
$startTime = (Get-Date).AddDays(-14)
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4688; StartTime=$startTime} -ErrorAction SilentlyContinue |
Where-Object { $_.Message -match 'w3wp\.exe' -and $_.Message -match 'cmd\.exe|powershell\.exe|pwsh\.exe|cscript\.exe|wscript\.exe|mshta\.exe|certutil\.exe|bitsadmin\.exe|curl\.exe|wget\.exe' } |
Select-Object TimeCreated, Message |
Out-File $reportPath -Append
# --- 4. Check IIS logging is enabled and capturing required fields ---
"`n[4] IIS Logging Configuration" | Out-File $reportPath -Append
Import-Module WebAdministration -ErrorAction SilentlyContinue
Get-WebSite | ForEach-Object {
$logFile = Get-WebConfigurationProperty -Filter "system.applicationHost/sites/site[@name='$($_.Name)']/logFile" -Name "logExtFileFlags" -ErrorAction SilentlyContinue
"Site: $($_.Name) | State: $($_.State) | LogFlags: $logFile" | Out-File $reportPath -Append
}
# --- 5. Restrict write permissions on web root to prevent unauthorized file deployment ---
"`n[5] NTFS Permissions on Web Root (review for excessive write access)" | Out-File $reportPath -Append
foreach ($p in $optiPaths) {
if (Test-Path $p) {
$acl = Get-Acl $p
$acl.Access | Where-Object { $_.FileSystemRights -match 'Write|FullControl|Modify' -and $_.IdentityReference -match 'IUSR|IIS_IUSRS|Everyone|Users|Network Service' } |
Select-Object IdentityReference, FileSystemRights, AccessControlType |
Out-File $reportPath -Append
}
}
# --- 6. Check for unauthorized local admin accounts (common post-exploitation artifact) ---
"`n[6] Local Administrators Group Membership" | Out-File $reportPath -Append
Get-LocalGroupMember -Group "Administrators" -ErrorAction SilentlyContinue |
Select-Object Name, ObjectClass, PrincipalSource |
Out-File $reportPath -Append
"`n=== Assessment Complete ===" | Out-File $reportPath -Append
"Review findings in: $reportPath"
Write-Host "`nAudit complete. Report saved to: $reportPath" -ForegroundColor Green
Write-Host "ACTION REQUIRED: Review sections 2 and 3 for web shell indicators." -ForegroundColor Yellow
Write-Host "Patch Optimizely CMS immediately per vendor advisory." -ForegroundColor Red
Remediation
Immediate Actions (Within 24 Hours)
- Patch Optimizely CMS to the latest supported version. Contact Optimizely support or consult the vendor advisory at https://www.optimizely.com/ to obtain the specific fixed version for your deployment. Do not delay — active exploitation is confirmed.
- Audit all Optimizely-hosted web properties for compromise. Run the PowerShell assessment script above on every server hosting Optimizely CMS. Focus on recently created script files in web-served directories and suspicious child processes of
w3wp.exe. - Review IIS access logs for the past 30 days. Look for anomalous POST requests to upload endpoints, requests with unusual User-Agent strings, and any requests returning 200 responses to paths that do not correspond to legitimate CMS content.
- Isolate any host showing indicators of compromise. Do not simply delete suspicious files — preserve forensic evidence, capture memory, and initiate your incident response plan before remediation.
Short-Term Hardening (Within 1 Week)
- Restrict IIS application pool identity permissions. The Optimizely application pool identity should have read-only access to the web root except for explicitly designated upload/media directories. No write access to directories serving executable content.
- Deploy a Web Application Firewall (WAF) with virtual patching rules targeting CMS exploitation patterns. If you already have a WAF, verify it is in blocking mode and rules are current.
- Enable and centralize IIS advanced logging. Capture
cs(User-Agent),cs(Referer),sc-status,sc-bytes, andtime-takenfields. Forward all logs to your SIEM with a minimum 90-day retention. - Implement file integrity monitoring (FIM) on all web-served directories. Alert on any file creation or modification outside of a documented deployment window.
Medium-Term Controls (Within 30 Days)
- Segment your CMS infrastructure. Web servers running Optimizely should reside in a DMZ with no direct access to internal networks, databases on separate segments, and no domain trust relationships beyond what is operationally required.
- Establish a CMS patching SLA. CMS platforms are high-value targets. Your vulnerability management program should classify CMS critical vulnerabilities as 24-48 hour patch requirements, not standard 30-day cycles.
- Conduct a compromise assessment across all Optimizely properties, including reviewing outbound DNS queries, TLS certificate transparency logs for your domains, and CDN access logs for anomalous content serving patterns.
Category
vulnerability-management
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.