# CVE-2025-62777: Hardcoded credentials in MZK-DP300N

> Hard-coded credentials allow local network attackers to log in via Telnet and execute arbitrary commands on the device.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-423r-r42q-j5mc

## What is CVE-2025-62777?

CVE-2025-62777 is a high-severity vulnerability in PLANEX COMMUNICATIONS INC. MZK-DP300N, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2025-62777?


## How do I fix CVE-2025-62777?

No fix has been published for CVE-2025-62777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62777 being exploited?

There is no known exploitation of CVE-2025-62777 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62777 and fix it if it is affected.

What it is: CVE-2025-62777 is a high-severity vulnerability in PLANEX COMMUNICATIONS INC. MZK-DP300N, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62777 in the wild and no public exploit code.

Affected product: PLANEX COMMUNICATIONS INC. MZK-DP300N. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62777/ (Markdown: https://insights.sbomify.com/CVE-2025-62777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62777
- OSV: https://osv.dev/vulnerability/CVE-2025-62777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62777/
Summaries are generated and may contain mistakes; the official description above is the record.