Loading vulnerability…
CVE-2013-10037 is an OS command injection vulnerability in WebTester 5.x, specifically in the install2.php installation script. The cpusername, cppassword, and cpdomain POST parameters are incorporated into shell commands without proper sanitization or neutralization of special elements. An attacker can send a crafted HTTP POST request to install2.php and inject arbitrary operating system commands for execution by the underlying shell. The issue is remotely exploitable and does not require authentication, provided the vulnerable installation script is reachable.
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/webapp/webtester_exec.rb) that exploits a remote command execution vulnerability in WebTester version 5.x (CVE-2013-10037). The exploit targets the 'install2.php' file, which is accessible without authentication, and injects commands via the 'cpusername', 'cppassword', or 'cpdomain' POST parameters. The module checks for the presence and version of WebTester by inspecting the HTTP response body for version strings. If vulnerable, it sends a POST request with a payload that results in arbitrary command execution on the target server. The exploit is weaponized, allowing customizable payloads and is suitable for operational use. The only fingerprintable endpoint is the '/webtester5/install2.php' path, which is the focus of the attack. The code is written in Ruby and is structured as a standard Metasploit exploit module.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.