# CVE-2023-7329: Tinycontrol LAN Controller v3 (LK3) Remote DoS

> Unauthenticated attackers can remotely reboot or reset Tinycontrol LAN Controllers, causing denial of service and configuration loss.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-2h8p-f7xr-xcpg

## What is CVE-2023-7329?

CVE-2023-7329 is a high-severity missing authorization vulnerability in tinycontrol Lan Controller, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tinycontrol LAN Controller v3 (LK3) firmware versions up to 1.58a (hardware v3.8) contain a missing authentication vulnerability in the stm.cgi endpoint. A remote, unauthenticated attacker can send crafted requests to forcibly reboot the device or restore factory settings, leading to a denial of service and configuration loss.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-7329?


## How do I fix CVE-2023-7329?

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

## Is CVE-2023-7329 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7329 and fix it if it is affected.

What it is: CVE-2023-7329 is a high-severity missing authorization vulnerability in tinycontrol Lan Controller, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7329 in the wild and no public exploit code.

Affected product: tinycontrol Lan Controller. 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-2023-7329/ (Markdown: https://insights.sbomify.com/CVE-2023-7329/index.md)
```

## Sources

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

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