Loading vulnerability…
A command injection vulnerability exists in Watchguard XCS versions 9.2 and 10.0 prior to build 150522. The vulnerability is due to improper sanitization of the 'id' parameter in the ADMIN/mailqueue.spl endpoint, allowing remote authenticated users 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/freebsd/http/watchguard_cmd_exec.rb) targeting Watchguard XCS virtual appliances (versions 9.2 and 10.0) running on BSD. The exploit leverages two vulnerabilities: an unauthenticated SQL injection to create a new web user, and a command injection in the web interface to achieve remote code execution as the 'nobody' user. The module automates the process of adding a backdoor user (if necessary), logging in, exploiting the command injection, and delivering a custom ELF payload (such as a reverse shell) to the target via HTTP. The exploit interacts with several web endpoints on the target, including /borderpost/imp/compose.php3 (for SQLi), /login.spl (for authentication), and /ADMIN/mailqueue.spl (for command injection). The payload is dropped to /tmp on the target and executed. The module is operational and provides reliable remote code execution capabilities.
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.