CVE-2022-25061 is a command injection vulnerability in TP-LINK TL-WR840N firmware version TL-WR840N(ES)_V6.20_180709. The issue was reported in the component/function oal_setIp6DefaultRoute. Based on the available description, insufficient neutralization of attacker-controlled input allows crafted data reaching this component to be interpreted as operating system commands.
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-25061, a remote command execution vulnerability in the TP-Link WR840N router. The main exploit script (CVE-2022-25061.py) is written in Python and automates the exploitation process by sending crafted HTTP POST requests to the router's '/cgi?2' endpoint. The exploit requires valid administrator credentials and the IP address of the target router. The attack proceeds in multiple stages: it first uploads a reverse shell binary (reverse_shell_mipsle.c, compiled for MIPSLE) to the router via TFTP, then sets permissions and executes it. The reverse shell binary, once running on the router, connects back to the attacker's machine, providing a remote shell. The repository structure is straightforward: the Python script is the exploit, the C file is the reverse shell payload, and the README provides a brief description. The exploit is operational and requires the attacker to set up a TFTP server and compile the reverse shell for the appropriate architecture.
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.
2 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.