A command injection vulnerability exists in TP-LINK TL-WR840N(ES)_V6.20_180709 via the oal_startPing component. The vulnerability allows an attacker to inject arbitrary commands into the system by exploiting insufficient input sanitization in the ping functionality.
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 an exploit for CVE-2022-25060, a remote command execution vulnerability in the TP-Link WR840N router. The main exploit script (CVE-2022-25060.py) is written in Python and requires the attacker's TFTP server (lhost), the target router's IP, and valid admin credentials. The script crafts a malicious request to the router's /cgi?2 endpoint, injecting a command to download a MIPSLE reverse shell binary (reverse_shell_mipsle.c, to be compiled and hosted by the attacker) via TFTP, set it as executable, and run it. The exploit then triggers the vulnerability via the /cgi?7 endpoint. The reverse shell binary, once executed on the router, connects back to the attacker's machine, providing a remote shell. The repository structure is straightforward: the Python exploit script, a C source file for the reverse shell (to be compiled for MIPSLE), and a brief README. The exploit is operational, requiring some setup (TFTP server, compilation of the payload) but provides a working remote shell if successful.
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.