# CVE-2025-66315: ZTE MF258K Pro Version Server has a Configuration Defect Vulnerability

> An attacker can exploit improper directory permissions to write files in a specific directory on the ZTE MF258K Pro version server.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 9 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-q363-5cqv-4f8m

## What is CVE-2025-66315?

CVE-2025-66315 is a medium-severity vulnerability in ZTE MF258K, published on 9 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

There is a configuration defect vulnerability in the version server of ZTE MF258K Pro products. Due to improper directory permission settings, an attacker can execute write permissions in a specific directory.

Weakness: CWE-863 (Incorrect Authorization), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Zte Mf258k Pro Firmware.

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

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

## Is CVE-2025-66315 being exploited?

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

## Other vulnerabilities in ZTE MF258K

- [CVE-2024-22065](https://insights.sbomify.com/CVE-2024-22065/): ZTE MF258 Pro product has a OS Command injection vulnerability (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66315 is a medium-severity vulnerability in ZTE MF258K, published on 9 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-66315 in the wild and no public exploit code.

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

## Sources

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

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