CVE-2026-58457
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedShenzhen Aitemi M300 Wi-Fi Repeater (hardware model MT02) contains an unauthenticated OS command injection vulnerability that allows network-adjacent attackers to execute arbitrary shell commands by injecting unsanitized input through the smacfilter_conf handler in the commuos web backend. Attackers can append semicolon-delimited payloads to the name, enable, or mac GET parameters, which are passed without sanitization into sprintf() to build uci shell commands executed via doSystemCmdComlib(), granting full root-level control of the device.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Shenzhen Aitemi M300 Wi-Fi Repeater (MT02) has an unauthenticated OS command injection vulnerability in the commuos web backend's smacfilter_conf handler. Attackers can inject shell commands via the name, enable, or mac GET parameters, which are passed unsanitized into sprintf() to construct uci commands executed by doSystemCmdComlib(), achieving full root-level control.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLocate the device label or check the web interface footer/admin page for the model name and version. Confirm it is the Shenzhen Aitemi M300 Wi-Fi Repeater (MT02).Affected if The device is an Aitemi M300 (MT02) Wi-Fi Repeater.
-
Confirm commuos web backend is presentAccess the device's web interface via HTTP/HTTPS (typically the IP assigned to the repeater). Look for signs of the 'commuos' backend in the HTML source, headers, or known management paths.Affected if The device runs the commuos web backend.
-
Check if smacfilter_conf endpoint is accessibleAttempt to access the smacfilter_conf handler via a GET request to a likely path such as /cgi-bin/commuos/smacfilter_conf or /cgi-bin/smacfilter_conf (the exact path is not specified, so probe common cgi-bin locations).Affected if The smacfilter_conf handler responds to requests.
-
Verify network exposure of management interfaceDetermine if the device's web management interface is reachable from untrusted networks. Check if it is behind a firewall or on an isolated network segment.Affected if The web interface is directly accessible from adjacent networks without network segmentation.
A user is affected if they operate a Shenzhen Aitemi M300 (MT02) device with the commuos web backend where the smacfilter_conf endpoint is network-accessible, allowing unauthenticated attackers to inject commands via the name, enable, or mac GET parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware patch when available; until then, restrict network access to the device's web interface via network segmentation or firewall rules to prevent adjacent attackers from reaching the management interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58457 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data