# CVE-2025-14105: TOZED ZLT M30S/ZLT M30S PRO Web proc_post denial of service

> An attacker on the local network can cause a denial of service by sending a specific reboot command to the web interface.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 5 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-wcg6-hc2x-j38j

## What is CVE-2025-14105?

CVE-2025-14105 is a medium-severity denial of service vulnerability in TOZED ZLT M30S, published on 5 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in TOZED ZLT M30S and ZLT M30S PRO 1.47/3.09.06. This impacts an unknown function of the file /reqproc/proc_post of the component Web Interface. Executing manipulation of the argument goformId with the input REBOOT_DEVICE can lead to denial of service. The attack can only be done within the local network. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2025-14105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14105 is a medium-severity denial of service vulnerability in TOZED ZLT M30S, published on 5 Dec 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-14105 in the wild and no public exploit code.

Affected product: TOZED ZLT M30S. 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-14105/ (Markdown: https://insights.sbomify.com/CVE-2025-14105/index.md)
```

## Sources

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

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