An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote attackers to upload arbitrary files to the server’s filesystem. By abusing the upload handler and crafting a traversal path, an attacker can place a malicious .exe in system32, followed by a .mof file in the WMI directory. This triggers execution of the payload with SYSTEM privileges via the Windows Management Instrumentation service. The exploit is only viable on Windows versions prior to Vista.
Security readout for executives and security teams
Plain-English summary
MiniWeb HTTP Server up to Build 300 has an unauthenticated file upload flaw that can let an attacker place files on the server. On vulnerable pre-Vista Windows systems, the described abuse can lead to SYSTEM-level code execution. This is most urgent for legacy Windows systems exposed to the internet.
Executive priority
Escalate immediately if MiniWeb <= Build 300 is exposed on legacy Windows. For modern Windows or non-exposed deployments, prioritize verification and removal, but avoid declaring compromise without evidence.
Technical view
The issue is CWE-434 unrestricted file upload in MiniWeb <= Build 300. The source bundle describes abuse of the upload handler with path traversal to place attacker-controlled files, enabling SYSTEM execution through Windows Management Instrumentation behavior on Windows versions before Vista.
Likely exposure
Exposure is likely limited to MiniWeb deployments at or below Build 300, especially legacy Windows hosts before Vista. Internet-facing instances are highest risk. The affected metadata is incomplete, so asset discovery should not rely only on CPE matching.
Exploitation context
Public exploit references exist in Metasploit and Exploit-DB, but the bundle does not show CISA KEV listing or confirmed active exploitation. The exploitability condition is narrower than the CVSS score suggests because the described SYSTEM execution path applies only before Windows Vista.
Researcher notes
The source bundle cites public exploit material and a third-party advisory, but KEV is false. Affected-product metadata is weak, listing version 0 with unknown default status, so validation should combine service fingerprinting, build checks, and OS confirmation.
Mitigation direction
Inventory MiniWeb deployments and identify any at or below Build 300.
Remove or replace MiniWeb on unsupported legacy Windows hosts.
Restrict MiniWeb access from the internet until vendor guidance is confirmed.
Disable upload capability where operationally possible.
Check MiniWeb and VulnCheck guidance for any fixed build or vendor mitigation.
Prioritize isolation and rebuild if compromise is suspected.
Validation and detection
Search asset inventories for MiniWeb HTTP Server deployments.
Confirm MiniWeb build numbers and host operating system versions.
Check whether any MiniWeb instance is internet-facing.
Review web server upload locations for unexpected executable or system files.
Inspect relevant Windows and web logs for unauthenticated upload activity.
Document findings where version or OS evidence is incomplete.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.