Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighPublic exploit

Windows PowerShell Invoke-WebRequest Command Injection RCE

IdentifiersCVE-2025-54100CWE-77· Improper Neutralization of Special…

CVE-2025-54100 is a Windows PowerShell remote code execution vulnerability caused by improper neutralization of special elements used in a command. The issue is described as a command injection flaw in how Windows PowerShell processes web content, particularly in scenarios involving Invoke-WebRequest (also referenced in some reporting as the curl alias in PowerShell). Multiple sources in the provided content state that a PowerShell script using Invoke-WebRequest may execute scripts included in the HTTP response, and that crafted response bodies can trigger vulnerable parser logic. Successful exploitation results in execution in the security context of the user running the PowerShell command. The vulnerability was publicly disclosed prior to patch availability and is rated Important with a reported CVSS score of 7.8.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can achieve arbitrary code execution in the context of the user who runs the vulnerable PowerShell command. Depending on that user's privileges, this can enable malware execution, implant delivery, persistence, access to local data accessible to the user, and potentially follow-on privilege escalation or lateral movement. In enterprise environments that rely heavily on PowerShell for administration and automation, the flaw creates risk in scripted workflows that retrieve remote content.

Mitigation

If you can’t patch tonight, do this now.

Where patching cannot be performed immediately, avoid using Invoke-WebRequest against untrusted or unnecessary remote content and prefer the safer parsing mode referenced by Microsoft. The provided content specifically notes Microsoft's recommendation to use the -UseBasicParsing parameter to avoid script execution. Additional practical mitigations supported by the context include restricting PowerShell usage to trusted administrators and workflows, enforcing least privilege, hardening execution policies, and monitoring PowerShell logging and command-line telemetry for suspicious web-retrieval and script-execution patterns.

Remediation

Patch, then assume compromise.

Apply Microsoft's December 2025 security update for Windows PowerShell addressing CVE-2025-54100. The provided content indicates that fully addressing the issue may require a reboot after patch installation. After the update, PowerShell displays a security warning when Invoke-WebRequest is used; administrators should validate operational scripts for compatibility with this behavior and update automation as needed.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).

VALID 2 / 4 TOTALView more in app
CVE-2025-54100MaturityPoCVerified exploit

This repository is a proof-of-concept (PoC) exploit for CVE-2025-54100, a remote code execution vulnerability affecting Windows PowerShell 5.1 when using Invoke-WebRequest without the -UseBasicParsing flag. The repository contains four files: a Python FastAPI server (app.py), a README.md with detailed usage and background, a requirements.txt for dependencies, and a LICENSE. The main exploit logic is in app.py, which serves a crafted HTML payload at the root HTTP endpoint. When a vulnerable Windows system accesses this endpoint (e.g., via Invoke-WebRequest or mshta), the HTML/JavaScript attempts to instantiate ActiveX objects to execute calc.exe, demonstrating RCE. The exploit is non-destructive and intended for research/validation. The README provides clear instructions for setup, exploitation, and mitigation. No hardcoded IPs are present in the code, but the README uses example IPs for demonstration. The attack vector is network-based, requiring the victim to access the attacker's HTTP server. The auxiliary /log endpoint is present for client-side logging but is not essential to the exploit. The PoC is mature as a demonstration but not weaponized for broader attacks.

xiaoLvChenDisclosed Dec 29, 2025pythonhtmlnetwork
CVE-2025-54100MaturityPoCVerified exploit

This repository provides a proof-of-concept (PoC) exploit for CVE-2025-54100, a command injection vulnerability in Windows PowerShell 5.1's Invoke-WebRequest cmdlet. The repository contains four files: a Python exploit script (CVE-2025-54100.py), a README.md with detailed vulnerability and usage information, a .gitignore, and a requirements.txt listing FastAPI and Uvicorn as dependencies. The main exploit script implements a FastAPI web server that serves a crafted HTML/JavaScript payload at the root endpoint ('/'). When a vulnerable Windows PowerShell client fetches this endpoint using Invoke-WebRequest (without the -UseBasicParsing switch), the response is parsed by the MSHTML engine, which executes the embedded script. The current payload is non-malicious and simply triggers an alert for verification, but the mechanism demonstrates the potential for remote code execution. The exploit is network-based, requiring the victim to connect to the attacker's server. The repository is structured for easy use and testing, with clear instructions and mitigation advice in the README.

ThemeHackersDisclosed Dec 13, 2025pythonnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity31

Community discussion across Reddit, Mastodon, and other social sources.