Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-58457 – Unauthenticated RCE – Shenzhen Aitemi M300 Wi-Fi Repeater (all versions)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58457 is a critical, unauthenticated OS command injection vulnerability in the Shenzhen Aitemi M300 Wi-Fi Repeater (hardware model MT02). The flaw resides in the smacfilter_conf handler of the device’s commuos web backend, enabling remote attackers to execute arbitrary shell commands as root with no credentials or user interaction required. The vulnerability carries a CVSS 4.0 score of 9.3 and a CVSS 3.1 score of 9.8, and no vendor patch is currently available.

Technical details

  • Root cause: The smacfilter_conf handler accepts the name, enable, and mac GET parameters and passes their values, without any sanitization or validation, into sprintf() to construct UCI shell commands.
  • Trigger conditions: An attacker sends a crafted HTTP GET request to the vulnerable endpoint, appending semicolon-delimited OS command payloads to any of the three affected parameters.
  • Execution path: The unsanitized string assembled by sprintf() is forwarded to doSystemCmdComlib(), which executes it directly as a shell command on the device.
  • Attack vector: Fully network-accessible and unauthenticated — no credentials, prior foothold, or user interaction are required.
  • Impact: Complete root-level remote code execution (UID 0) on the affected device, enabling full device takeover, persistent backdoor installation, manipulation of wireless and WAN configurations, and use of the device as a network pivot point.

Affected software

  • Shenzhen Aitemi M300 Wi-Fi Repeater, hardware model MT02 — all versions

Severity

  • CVSS 4.0: 9.3 Critical — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CVSS 3.1: 9.8 Critical — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • No vendor patch is currently available for CVE-2026-58457.
  • Immediate workarounds:
    • Immediately remove affected MT02 devices from internet-facing deployments; restrict web management interface access to trusted local network segments only, using firewall rules to block all inbound WAN access to the management port.
    • If local-only access cannot be enforced, consider replacing the device with a supported alternative that receives active security updates.
    • Monitor affected devices for anomalous outbound connections, unexpected configuration changes, or unfamiliar processes indicative of post-exploitation activity.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge