CVE-2026-58457 is a critical unauthenticated OS command injection vulnerability in the Shenzhen Aitemi M300 Wi-Fi Repeater, hardware model MT02. The flaw is in the commuos web backend, specifically the smacfilter_conf handler. User-controlled GET parameters name, enable, and mac are incorporated without sanitization into uci shell command strings using sprintf(), and those commands are then executed via doSystemCmdComlib(). By appending semicolon-delimited shell payloads to one of the vulnerable parameters, a network-adjacent attacker can cause arbitrary operating system commands to be executed on the device. Because the commands run in the device context with root privileges, successful exploitation results in full compromise of the repeater.
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 real exploit set for CVE-2026-58457, an unauthenticated OS command injection vulnerability in the Shenzhen Aitemi M300 Wi-Fi Repeater (MT02). Because the repository includes a Metasploit module, the primary exploit file is aitemi_m300_smacfilter_rce.rb. That module is a weaponized Metasploit exploit using Msf::Exploit::Remote::HttpClient and Msf::Exploit::CmdStager. It targets the device’s web interface on port 80 by default, optionally over SSL, and attempts injection through the GET parameters name, enable, or mac. The injected payload format is ;<cmd>;, and the module iterates across four candidate paths: /goform/smacfilter_conf, /form/smacfilter_conf, /smacfilter_conf, and /apply.cgi. The check routine uses a harmless id command and marks the target vulnerable if the HTTP response contains uid/gid output. Exploitation supports two modes: direct Unix command execution and staged Linux MIPSBE payload delivery via CmdStager, indicating practical post-exploitation capability beyond a simple proof of concept. Repository structure beyond the Metasploit module includes poc.py, a standalone Python exploit that performs the same unauthenticated GET-based command injection over HTTP/HTTPS with retries and optional callback-based output exfiltration using curl or wget; val.py, a passive validator that checks for vulnerability using id and response matching; gen.py, a payload generator that creates obfuscated command-injection strings using URL encoding, double encoding, base64, hex, IFS substitution, subshells, backticks, eval, printf, and randomized separators; plus README.md and MITIGATIONS.md for usage and defensive guidance. Overall, the repository’s purpose is to provide offensive testing and validation tooling for this router/repeater RCE, with both framework-integrated and standalone exploit paths.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.