Rockwell FactoryTalk Viewpoint privilege escalation via MSI repair
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Local privilege escalation in FactoryTalk Viewpoint via MSI repair operations allows SYSTEM access; patch to version 15.00+.
Rockwell Automation FactoryTalk Viewpoint versions 14.00 and prior contain a privilege escalation vulnerability (CVE-2025-7973) stemming from improper handling of MSI repair operations. An attacker with local access and low privileges can hijack the cscript.exe console window—which executes with SYSTEM privileges during repair—to spawn an elevated command prompt and achieve full privilege escalation.
The vulnerability has a CVSS v4 score of 8.5 and requires local access; it is not exploitable remotely. No active exploitation in the wild has been reported to CISA as of the advisory date. Defenders should prioritize upgrading to version 15.00 or later. For organizations unable to upgrade immediately, CISA recommends segmenting ICS networks from the internet and business networks, restricting local access, and enforcing VPN and firewall controls for remote access.
Mentioned in this report
Detection guidance
SYSTEM Command Shell Spawned from Conhost or Cscript Console
A SYSTEM-level cmd.exe or PowerShell spawned by conhost.exe or cscript.exe, consistent with console window hijacking during an MSI repair (CVE-2025-7973 style). 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: SYSTEM Command Shell Spawned from Conhost or Cscript Console
id: fd664a90-cac2-5c87-b627-60dde26ddbc1
status: experimental
description: Detects cmd.exe or PowerShell running as SYSTEM with conhost.exe or cscript.exe
as parent. This is the outcome of hijacking a SYSTEM console window (for example
one shown by cscript.exe during an MSI repair) to get an elevated shell. Conhost
and cscript do not normally launch interactive shells.
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-23
tags:
- attack.privilege-escalation
- attack.t1548.002
- attack.t1134.001
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith:
- \conhost.exe
- \cscript.exe
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
User|contains:
- AUTHORITY
- SYSTEM
condition: selection
falsepositives:
- Administrative logon or deployment scripts that launch cmd.exe from cscript.exe
under SYSTEM
- Software installers whose VBScript custom actions call cmd.exe during install or
repair
level: high
author: Vorant
Browser or Help Process Spawned by Conhost as SYSTEM
A browser or file-dialog capable process spawned by conhost.exe under SYSTEM, the usual intermediate step in hijacking a SYSTEM console window to reach a shell. 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: Browser or Help Process Spawned by Conhost as SYSTEM
id: 59db5b7c-2d55-5c92-94a0-71dd4c42155b
status: experimental
description: Detects conhost.exe spawning a web browser, mshta or explorer as SYSTEM.
This follows from interacting with a SYSTEM console window (title-bar properties
or hyperlink) and is used to pivot to an elevated cmd.exe through an open or save
dialog.
tags:
- attack.privilege-escalation
- attack.t1548.002
- attack.t1134.001
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: \conhost.exe
Image|endswith:
- \iexplore.exe
- \msedge.exe
- \chrome.exe
- \firefox.exe
- \mshta.exe
- \explorer.exe
User|contains:
- AUTHORITY
- SYSTEM
condition: selection
falsepositives:
- Rare administrative troubleshooting performed in a SYSTEM session
level: high
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-23
Cscript Launched by Msiexec as SYSTEM
cscript.exe spawned by msiexec.exe under SYSTEM, the console window that is hijacked during a vulnerable MSI repair. Low-fidelity hunting rule. 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: Cscript Launched by Msiexec as SYSTEM
id: 450ecc65-c242-5ba5-803f-599ca21168aa
status: experimental
description: Detects msiexec.exe launching cscript.exe as SYSTEM, which occurs during
MSI repair or install custom actions. The visible cscript console runs with SYSTEM
privileges and can be hijacked by a low-privileged user. Use as a hunting or context
rule and correlate with child shells from conhost.exe or cscript.exe.
tags:
- attack.privilege-escalation
- attack.t1548.002
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: \msiexec.exe
Image|endswith: \cscript.exe
User|contains:
- AUTHORITY
- SYSTEM
condition: selection
falsepositives:
- Legitimate MSI packages that run VBScript custom actions during install, repair
or upgrade
level: low
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-23
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-23
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs