# CVE-2023-53739: Tinycontrol LAN Controller v3 LK3 1.58a Unauthenticated Configuration Backup Disclosure

> Remote attackers can download configuration backups to extract base64-encoded credentials, leading to unauthorized access.

- **Severity:** Critical 9.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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:** 9 Dec 2025
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-vqf5-jvfh-997c

## What is CVE-2023-53739?

CVE-2023-53739 is a critical vulnerability in Tinycontrol LK, published on 9 Dec 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 version 1.58a contains an unauthenticated vulnerability that allows remote attackers to download configuration backup files containing sensitive credentials. Attackers can retrieve the lk3_settings.bin file and extract base64-encoded user and admin passwords without authentication.

Weakness: CWE-260 (Password in Configuration File)

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


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

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

## Is CVE-2023-53739 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-53739 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53739 is a critical vulnerability in Tinycontrol LK, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-53739 exists.

Affected product: Tinycontrol LK. 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-53739/ (Markdown: https://insights.sbomify.com/CVE-2023-53739/index.md)
```

## Sources

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

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