# CVE-2025-68718: Hardcoded credentials in n/a

> KAYSUS KS-WR1200 routers expose SSH and TELNET with hardcoded root credentials, allowing LAN attackers to gain full administrative control.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A: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:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-83vm-9w92-6cqh

## What is CVE-2025-68718?

CVE-2025-68718 is a medium-severity vulnerability in n/a, published on 8 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

KAYSUS KS-WR1200 routers with firmware 107 expose SSH and TELNET services on the LAN interface with hardcoded root credentials (root:12345678). The administrator cannot disable these services or change the hardcoded password. (Changing the management GUI password does not affect SSH/TELNET authentication.) Any LAN-adjacent attacker can trivially log in with root privileges.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Kaysus Ks-Wr1200 Firmware.

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

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

## Is CVE-2025-68718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68718 is a medium-severity vulnerability in n/a, published on 8 Jan 2026. 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-68718 in the wild and no public exploit code.

Affected product: n/a. 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-68718/ (Markdown: https://insights.sbomify.com/CVE-2025-68718/index.md)
```

## Sources

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

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