CVE-2025-34149
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 · uneditedA command injection vulnerability affects the Shenzhen Aitemi M300 Wi-Fi Repeater (hardware model MT02) during WPA2 configuration. The 'key' parameter is interpreted directly by the system shell, enabling attackers to execute arbitrary commands as root. Exploitation requires no authentication and can be triggered during wireless setup.
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 confidenceCommand injection in the Shenzhen Aitemi M300 Wi-Fi Repeater (MT02) allows unauthenticated attackers to execute arbitrary commands as root via the 'key' parameter during WPA2 wireless configuration, which is directly interpreted by the system shell without sanitization.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 the device modelAccess the device web interface (typically 192.168.1.1 or 192.168.0.1) and check the device information page, or physically inspect the device label for 'Shenzhen Aitemi M300' or 'MT02' model markingsAffected if The device is a Shenzhen Aitemi M300 Wi-Fi Repeater (MT02)
-
Check if the web management interface is accessibleAttempt to access the device HTTP/HTTPS web interface on common management ports. The vulnerable configuration is accessible through the wireless setup or WPA2 settings pageAffected if The web interface is exposed and accepts wireless configuration parameters including a 'key' parameter for WPA2 passphrase
-
Verify the 'key' parameter accepts special charactersSubmit a test wireless configuration with a 'key' value containing shell metacharacters such as $(whoami) or ;ls. Observe if the device processes these characters or returns an error indicating command injection potentialAffected if The 'key' parameter does not sanitize shell metacharacters and appears to pass input directly to system shell execution
-
Check network exposure of the deviceDetermine if the device web management interface is accessible from untrusted network segments by scanning for open HTTP ports (80, 443, 8080) on the device IP addressAffected if The device management interface is accessible from outside isolated network segments without authentication barriers
The environment is affected if a Shenzhen Aitemi M300 Wi-Fi Repeater (MT02) device with an accessible web interface exists on the network, where the WPA2 'key' parameter in wireless configuration accepts unsanitized input that could be interpreted by the system shell.
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 dataIsolate affected devices on restricted network segments, monitor for indicators of compromise, and replace or restrict access to these devices until a vendor firmware patch is available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34149 — 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-2025-34149 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