CVE-2025-34152
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 · uneditedAn unauthenticated OS command injection vulnerability exists in the Shenzhen Aitemi M300 Wi-Fi Repeater (hardware model MT02) via the 'time' parameter of the '/protocol.csp?' endpoint. The input is processed by the internal date '-s' command without rebooting or disrupting HTTP service. Unlike other injection points, this vector allows remote compromise without triggering visible configuration changes.
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 confidenceUnauthenticated OS command injection in Shenzhen Aitemi M300 Wi-Fi Repeater (MT02) allows remote attackers to execute arbitrary commands via the 'time' parameter in the '/protocol.csp?' endpoint. The input is passed to the system's date '-s' command without disrupting service, enabling covert remote compromise.
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 device modelAccess the device's web interface or check the device label/management console to confirm the model is Shenzhen Aitemi M300 Wi-Fi Repeater (MT02)Affected if The device model is M300 (MT02) from Shenzhen Aitemi
-
Check web interface accessibilityAttempt to reach the device's IP address on port 80 or 443 via HTTP requestAffected if The device's web interface is accessible on the network
-
Verify vulnerable endpoint existsSend a request to the '/protocol.csp?' endpoint on the device (e.g., GET /protocol.csp?function=somevalue&time=test) and check for a responseAffected if The /protocol.csp endpoint responds to requests
-
Confirm firmware versionCheck the device's firmware version through its web admin panel or by querying its management interface, then compare against any vendor-published fixed versionsAffected if The firmware version has not been patched by the vendor
-
Assess network exposureDetermine whether the device's web interface is exposed to untrusted networks (e.g., directly to the internet, or on a network segment accessible to untrusted devices)Affected if The device is reachable from untrusted network segments without network segmentation
The device is affected if it is a Shenzhen Aitemi M300 Wi-Fi Repeater (MT02) with an accessible /protocol.csp endpoint, regardless of authentication, and the firmware has not been updated to a patched version.
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 network segmentation to isolate the device from untrusted networks; contact vendor for firmware update; block external access to the device's web interface.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34152 — 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-34152 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