CVE-2025-15587 json
Credentials exposure in tinycontrol devices
published 2026-03-16 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-208690
- cvss
- 8.6
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- tinycontrol Lan Kontroler v3.5 1.67
- tinycontrol LK3.9 1.75
- tinycontrol LK4 1.38
- tinycontrol tcPDU 1.36
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 7 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- tinycontrol Lan Kontroler v3.5
- tinycontrol LK3.9
- tinycontrol LK4
- tinycontrol tcPDU
Classification
- Weakness
-
- CWE-425 Direct Request
References
-
cert.pl
/en/posts/2026/03/CVE-2025-11500/
third-party-advisory
-
tinycontrol.pl
/en/archives/lan-controller-35/downloads/#firmware
release-notes
-
tinycontrol.pl
/en/lk39/downloads/#firmware
release-notes
-
tinycontrol.pl
/en/lk4/downloads/#firmware
release-notes
-
tinycontrol.pl
/en/tcpdu/downloads/#firmware
release-notes
Sources
- CVE List CVE-2025-15587
- NVD CVE-2025-15587
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.