dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-34150

CRITICAL · 9.4 CVSS v4.0 Published 2025-08-07
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
The PPPoE configuration interface of the Shenzhen Aitemi M300 Wi-Fi Repeater (hardware model MT02) is vulnerable to command injection via the 'user' parameter. Input is processed unsafely during network setup, allowing attackers to execute arbitrary system commands with root privileges.

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

The PPPoE configuration interface in the Shenzhen Aitemi M300 Wi-Fi Repeater (MT02) fails to sanitize input in the 'user' parameter during network setup. This allows unauthenticated attackers to inject and execute arbitrary OS commands with root privileges by crafting malicious input in the PPPoE user field.

MitigationUntil a vendor patch is available, disable or restrict access to the PPPoE configuration interface. If feasible, implement input validation to reject shell metacharacters in the user parameter, and consider network segmentation to limit exposure of the management interface.

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. Confirm device model is Aitemi M300 (MT02)
    Check device label, web interface status page, or DHCP client hostname for 'Aitemi M300' or 'MT02'
    Affected if Device is a Shenzhen Aitemi M300 Wi-Fi Repeater (MT02)
  2. Check firmware version
    Access device web interface and navigate to System or Status page to view firmware version
    Affected if Firmware version is unpatched (compare to any vendor release notes if available)
  3. Locate PPPoE configuration interface
    Access device web interface and navigate to Network or WAN settings to find PPPoE configuration options
    Affected if PPPoE configuration interface is present on the device
  4. Inspect the user parameter in PPPoE settings
    View the PPPoE configuration form HTML or intercept the HTTP request when saving settings to examine how the 'user' parameter is handled
    Affected if The 'user' field accepts input without visible sanitization or validation before being processed
  5. Determine network exposure of the device management interface
    Check router or firewall configurations to see if the device web interface is accessible from WAN or untrusted networks
    Affected if The PPPoE configuration interface is exposed to the internet or untrusted networks

If you have a Shenzhen Aitemi M300 (MT02) with an accessible PPPoE configuration interface, especially if exposed to untrusted networks, you are likely affected by this command injection vulnerability.

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

Until a vendor patch is available, disable or restrict access to the PPPoE configuration interface. If feasible, implement input validation to reject shell metacharacters in the user parameter, and consider network segmentation to limit exposure of the management interface.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34150 — 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-34150 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