# CVE-2025-15587: Credentials exposure in tinycontrol devices

> Low-privileged users can read administrator passwords by accessing a hidden resource, enabling privilege escalation on Tinycontrol devices.

- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-p5qr-79pr-g4vp

## What is CVE-2025-15587?

CVE-2025-15587 is a high-severity vulnerability in tinycontrol LK3.9, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tinycontrol devices such as tcPDU and LAN Controllers LK3.5, LK3.9 and LK4 allow a low privileged user to read an administrator's password by directly accessing a specific resource inaccessible via a graphical interface.

This issue has been fixed in firmware versions: 1.36 (for tcPDU), 1.67 (for LK3.5 - hardware versions: 3.5, 3.6, 3.7 and 3.8), 1.75 (for LK3.9 - hardware version 3.9) and 1.38 (for LK4 - hardware version 4.0).

Weakness: CWE-425 (Direct Request)

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


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

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

## Is CVE-2025-15587 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15587 is a high-severity vulnerability in tinycontrol LK3.9, published on 16 Mar 2026. 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-15587 in the wild and no public exploit code.

Affected product: tinycontrol LK3.9. 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-15587/ (Markdown: https://insights.sbomify.com/CVE-2025-15587/index.md)
```

## Sources

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

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