Loading vulnerability…
WAN Emulator v2.3 contains two command-injection issues that can be chained for full compromise. First, the result.php script invokes shell_exec() on attacker-controlled data from the pc POST parameter without proper sanitization, enabling unauthenticated remote command execution in the web application context as user www-data. Second, the product includes a SUID-root helper binary named dosu that is vulnerable to command injection through its first argument. An attacker who gains code execution via result.php can then invoke the vulnerable dosu binary to execute commands with root privileges, resulting in complete remote compromise of the host.
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/linux/http/wanem_exec.rb) targeting WAN Emulator version 2.3. The exploit leverages a command injection vulnerability in the 'result.php' script, which processes user input from the 'pc' parameter without proper sanitization, allowing unauthenticated remote attackers to execute arbitrary shell commands as the 'www-data' user. The module further exploits a SUID root binary ('dosu') present on the system to escalate privileges to root. The attack is performed over HTTP by sending a specially crafted POST request to '/WANem/result.php'. The module is fully weaponized, supporting customizable command payloads via the Metasploit framework, and provides both initial code execution and privilege escalation. The code is written in Ruby and follows standard Metasploit module structure.
6 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.