CVE-2025-14126
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 vulnerability has been found in TOZED ZLT M30S and ZLT M30S PRO 1.47/3.09.06. Affected is an unknown function of the component Web Interface. Such manipulation leads to hard-coded credentials. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceHard-coded credentials vulnerability in the web interface of TOZED ZLT M30S and M30S PRO routers (firmware 1.47/3.09.06). An attacker with local network access can exploit these static credentials to gain unauthorized administrative access to the device. The exploit has been publicly disclosed.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 modelLog into the router web interface or check the device label/marketing materials to confirm the exact model is TOZED ZLT M30S or M30S PROAffected if The device is a TOZED ZLT M30S or M30S PRO router
-
Check firmware version on M30SNavigate to the router web interface Status or System Information page and locate the firmware version field. Compare against version 1.47Affected if Firmware version is 1.47 or lower
-
Check firmware version on M30S PRONavigate to the router web interface Status or System Information page and locate the firmware version field. Compare against version 3.09.06Affected if Firmware version is 3.09.06 or lower
-
Verify web interface network exposureDetermine if the router web interface (typically ports 80 or 443) is accessible from network segments beyond the trusted local network. Check firewall rules and NAT configurationsAffected if Web interface is exposed to untrusted network segments or the internet
-
Audit administrative accountsReview the list of user accounts in the router web interface under User Management or Administration settings. Look for any unexpected or undocumented admin-level accountsAffected if Unexpected administrative accounts exist beyond those created by the administrator
If the device is a TOZED ZLT M30S or M30S PRO running firmware 1.47 or 3.09.06 or lower respectively, and the web interface is accessible from the local network, the environment is affected by this hard-coded credentials vulnerability
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 dataSince the vendor did not respond to the disclosure, implement compensating controls: isolate affected devices on a restricted network segment, enforce strict firewall rules limiting web interface access to authorized management IPs only, and monitor for unauthorized access attempts. Consider replacing the device if no firmware update becomes available.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14126 — 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-14126 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