CVE-2025-11500: Credentials exposure in tinycontrol devices
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: tinycontrol Lan Kontroler v3.5 1.67; tinycontrol LK3.9 1.75; tinycontrol LK4 1.38.
Low priority for now. Upgrade to tinycontrol Lan Kontroler v3.5 1.67; tinycontrol LK3.9 1.75; tinycontrol LK4 1.38 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Tinycontrol devices such as tcPDU and LAN Controllers LK3.5, LK3.9 and LK4 have two separate authentication mechanisms - one solely for interface management and one for protecting all other server resources. When the latter is turned off (which is a default setting), an unauthenticated attacker on the local network can obtain usernames and encoded passwords for interface management portal by inspecting the HTTP response of the server when visiting the login page, which contains a JSON file with these details. Both normal and admin users credentials are exposed. 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).
- Published
- Mar 16, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-201
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERT-PL
- 8.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERT-PL). Independent of NVD's CPE analysis and usually ahead of it.
tinycontrol Lan Kontroler v3.5
- before 1.67affected · semver
tinycontrol LK3.9
- before 1.75affected · semver
tinycontrol LK4
- before 1.38affected · semver
tinycontrol tcPDU
- before 1.36affected · semver
Same product
tinycontrol: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-15587Credentials exposure in tinycontrol devices34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| tinycontrol Lan Kontroler v3.5 | 1.67 | Vendor (CNA) |
| tinycontrol LK3.9 | 1.75 | Vendor (CNA) |
| tinycontrol LK4 | 1.38 | Vendor (CNA) |
| tinycontrol tcPDU | 1.36 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.