# CVE-2025-68719: Information disclosure in n/a

> An attacker with an active session can download the router's configuration archive, exposing sensitive files like /etc/shadow and enabling credential recovery.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-3vfq-jv69-rjgp

## What is CVE-2025-68719?

CVE-2025-68719 is a high-severity vulnerability in n/a, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

KAYSUS KS-WR3600 routers with firmware 1.0.5.9.1 mishandle configuration management. Once any user is logged in and maintains an active session, an attacker can directly query the backup endpoint and download a full configuration archive. This archive contains sensitive files such as /etc/shadow, enabling credential recovery and potential full compromise of the device.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Kaysus Ks-Wr3600 Firmware.

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

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

## Is CVE-2025-68719 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-68717](https://insights.sbomify.com/CVE-2025-68717/): Auth bypass in n/a (critical 9.4)
- [CVE-2025-68716](https://insights.sbomify.com/CVE-2025-68716/): Hardcoded credentials in n/a (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68719 is a high-severity vulnerability in n/a, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68719 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-68719/ (Markdown: https://insights.sbomify.com/CVE-2025-68719/index.md)
```

## Sources

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

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