Loading vulnerability…
A command injection vulnerability exists in vmtadmin.cgi in VMTurbo Operations Manager prior to version 4.6 build 28657. The vulnerability is due to improper sanitization of the fileDate parameter in a DOWN call, allowing remote attackers to inject and execute arbitrary shell commands via shell metacharacters.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/unix/http/vmturbo_vmtadmin_exec_noauth.rb) that exploits an unauthenticated OS command injection vulnerability (CVE-2014-5073) in VMTurbo Operations Manager versions 4.6 and earlier (build < 28657). The exploit targets the /cgi-bin/vmtadmin.cgi HTTP endpoint, injecting commands via GET parameters. The module supports both direct command execution and staged payloads (such as reverse shells) using Metasploit's CmdStager. The exploit is blind, meaning no output is returned from executed commands. The module includes a version check to determine if the target is vulnerable. The code is written in Ruby and is designed to be used within the Metasploit framework. No hardcoded IPs or external domains are present; the only fingerprintable endpoint is the vulnerable CGI script on the target server.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.