CVE-2023-39780 is an authenticated OS command injection vulnerability affecting ASUS RT-AX55 devices running firmware 3.0.0.4.386.51598. The flaw is exposed through the /start_apply.htm endpoint via the qos_bw_rulelist parameter, where insufficient input filtering allows attacker-controlled data to be interpreted as operating system commands. Successful exploitation enables execution of arbitrary system-level commands in the router environment. The issue has been associated with later ASUS advisories covering closely related token-handling modules and has been used in real-world compromise chains against ASUS routers.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific CVE for which exploit code is implemented in native C inside TuxBot, but the exploit engine is dead code and never called at runtime in the analyzed version.
Unknown (vulnerability exploited by the AyySSHush/ViciousTrap botnet; mentioned as a shared/overlapping vulnerability with the WrtHug cluster).
Major command injection vulnerability in ASUS WRT routers, reported as used in both Operation WrtHug and the earlier AyySSHush campaign.
A command injection vulnerability affecting ASUS devices, associated with AyySSHush and referenced as related to several WrtHug vulnerabilities, but not directly confirmed here as one of the six primary WrtHug vulnerabilities.
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.