A command injection vulnerability exists in the D-Link DIR-600 (Hardware Version B5, Firmware Version 2.18) due to improper sanitization of the ST parameter in the lxmldbc_system() function. An attacker can inject arbitrary commands via this parameter, which are then executed with the privileges of the underlying system process.
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 (Ruby file) that exploits a command injection vulnerability in the UPnP implementation of multiple D-Link router models. The exploit works by sending a specially crafted UDP M-SEARCH packet to the target device's UPnP service (typically on UDP port 1900), injecting a shell command into the ST (Search Target) field. If the target is vulnerable, the command is executed as root, granting full remote code execution. The module supports both direct command execution and staged payloads (such as Meterpreter), and includes logic to fingerprint the device and check firmware versions via HTTP. The exploit targets a wide range of D-Link routers and firmware versions, as listed in the module's description, and is associated with several CVEs (CVE-2023-33625, CVE-2020-15893, CVE-2019-20215). The code is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The main attack vector is network-based, requiring access to the target's UDP port 1900.
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.