Loading vulnerability…
CVE-2013-10048 is an unauthenticated OS command injection vulnerability affecting various legacy D-Link routers, including DIR-300 rev B and DIR-600 devices running firmware versions up to 2.13 and 2.14b01 respectively. The issue is present in the command.php endpoint, which fails to properly authenticate requests and inadequately sanitizes the POST cmd parameter before passing attacker-controlled input to the underlying shell. A remote attacker can send a specially crafted POST request to command.php and cause arbitrary operating system commands to be executed with root privileges on the device.
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 targeting unauthenticated remote command execution vulnerabilities in certain D-Link routers (notably DIR-600 2.14b01 and DIR-300 rev B 2.13). The exploit leverages a command injection flaw in the /command.php endpoint, which is accessible without authentication. The module sends a POST request to /command.php with a payload that starts a telnet daemon on a random high port. It then attempts to connect to this telnet service, providing the attacker with an interactive shell on the device. The exploit is operational and provides a working shell if the target is vulnerable. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.
5 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.