CVE-2025-62777
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 · uneditedUse of Hard-Coded Credentials issue exists in MZK-DP300N version 1.07 and earlier, which may allow an attacker within the local network to log in to the affected device via Telnet and execute arbitrary commands.
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 confidenceA hard-coded credential vulnerability exists in MZK-DP300N wireless network devices version 1.07 and earlier. The device contains embedded Telnet credentials that cannot be changed by users, allowing any attacker with local network access to authenticate to the device's Telnet service and execute arbitrary commands with elevated privileges.
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.0/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.
-
Confirm router model is MZK-DP300NAccess the router web administration interface and locate the device information page, or physically inspect the device label. Alternatively, log into the router via CLI and run 'cat /proc/cpuinfo' or 'nvram get model' if available.Affected if The identified model is MZK-DP300N
-
Determine installed firmware versionIn the router web interface, navigate to the Status or System Information page to display the firmware version. Alternatively, check via CLI using 'nvram get firmware_version' or 'cat /proc/version' if SSH/Telnet is accessible.Affected if The firmware version is 1.07 or any version number lower than 1.07
-
Verify Telnet service statusFrom a workstation on the same network, attempt to connect to the router on Telnet port 23 using 'telnet <router_ip>' or run a port scan against the router IP for port 23/tcp.Affected if Port 23/tcp is open and accepts a login prompt, indicating Telnet is enabled
-
Test for hard-coded credential presenceAttempt to authenticate to the exposed Telnet service using the documented hard-coded credentials (if known from firmware analysis) or check the firmware binary for embedded strings matching credential patterns.Affected if Telnet login succeeds with credentials found embedded in the firmware binary or configuration files
-
Assess network exposure of Telnet serviceReview the router firewall or access control settings to determine if Telnet port 23 is accessible from LAN interfaces, WAN interfaces, or both.Affected if Telnet is accessible from any network segment beyond the trusted local network or from the WAN interface
A user is affected if they own an MZK-DP300N router running firmware version 1.07 or earlier with Telnet service enabled and accessible on their network.
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 dataRestrict network access to the Telnet port (TCP 23), disable Telnet if not required, and contact the vendor for a firmware update that removes hard-coded credentials. If Telnet is required, implement network segmentation to limit exposure.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62777 — 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-62777 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