dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-34147

CRITICAL · 9.4 CVSS v4.0 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
An unauthenticated OS command injection vulnerability exists in the Shenzhen Aitemi M300 Wi-Fi Repeater (hardware model MT02). When configuring the device in Extender mode via its captive portal, the extap2g SSID field is inserted unescaped into a reboot-time shell script. This allows remote attackers within Wi-Fi range to inject arbitrary shell commands that execute as root during device reboot, leading to full system compromise.

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 confidence

Unauthenticated OS command injection in Shenzhen Aitemi M300 Wi-Fi Repeater (MT02). The extap2g SSID field in the captive portal is not sanitized before being inserted into a reboot-time shell script, allowing remote attackers within Wi-Fi range to inject arbitrary commands that execute as root during device reboot.

MitigationReplace or retire the affected devices if no vendor firmware update is available; otherwise, apply vendor firmware patch. Until patched, restrict physical and Wi-Fi access to the device to trusted personnel only.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device's web interface or check the physical device label for the model number. Look for 'Aitemi M300' or 'MT02' marking on the device.
    Affected if The device is a Shenzhen Aitemi M300 or MT02 Wi-Fi Repeater.
  2. Verify captive portal accessibility
    Connect to the device's Wi-Fi network and attempt to access any HTTP URL to trigger the captive portal redirect. Alternatively, access the device's web management interface via its IP address.
    Affected if The captive portal or web management interface is accessible without authentication.
  3. Confirm the extap2g SSID field exists
    On the captive portal page, look for a configuration field labeled 'extap2g' or 'SSID' related to the 2.4GHz extended access point settings.
    Affected if The extap2g SSID configuration field is present in the captive portal.
  4. Check firmware version if exposed
    If accessible, navigate to the device status or firmware information page within the web interface to retrieve the installed firmware version.
    Affected if The firmware version cannot be verified as patched or is an older unreleased version.

A user is affected if they operate a Shenzhen Aitemi M300 (MT02) Wi-Fi Repeater with an accessible unauthenticated captive portal containing the extap2g SSID field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace or retire the affected devices if no vendor firmware update is available; otherwise, apply vendor firmware patch. Until patched, restrict physical and Wi-Fi access to the device to trusted personnel only.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34147 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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