CVE-2025-15083Public exploit

Wi-Fi credential disclosure via plaintext UART logs

Published Dec 25, 2025 · Updated Dec 25, 2025

Information disclosure in the UART console of TOZED ZLT M30S 1.0 through 1.47 allows physically proximate attackers to read Wi-Fi credentials. The debugging console logs the current credential during boot and the factory-set default credential during a factory reset without masking either value. Exploitation requires physical access and a connection to the device's UART interface; the reported consequence is credential disclosure rather than configuration changes or service interruption.

CVSS severity4.6
Medium
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in the UART console of TOZED ZLT M30S 1.0 through 1.47 allows physically proximate attackers to read Wi-Fi credentials. The debugging console logs the current credential during boot and the factory-set default credential during a factory reset without masking either value. Exploitation requires physical access and a connection to the device's UART interface; the reported consequence is credential disclosure rather than configuration changes or service interruption.

The record

CVE
CVE-2025-15083
Published
Dec 25, 2025
Updated
Dec 25, 2025
Vendor
Tozed Kangwei Tech Co., Ltd.
Product
ZLT M30S
Classifications
CWE-1191, T1552
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 25, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 25, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.0
  2. Affected versionversion=1.1
  3. Affected versionversion=1.10
  4. Affected versionversion=1.11
  5. Affected versionversion=1.12
  6. Affected versionversion=1.13
  7. Affected versionversion=1.14
  8. Affected versionversion=1.15
  9. Affected versionversion=1.16
  10. Affected versionversion=1.17
  11. Affected versionversion=1.18
  12. Affected versionversion=1.19
  13. Affected versionversion=1.2
  14. Affected versionversion=1.20
  15. Affected versionversion=1.21
  16. Affected versionversion=1.22
  17. Affected versionversion=1.23
  18. Affected versionversion=1.24
  19. Affected versionversion=1.25
  20. Affected versionversion=1.26
  21. Affected versionversion=1.27
  22. Affected versionversion=1.28
  23. Affected versionversion=1.29
  24. Affected versionversion=1.3
  25. Affected versionversion=1.30
  26. Affected versionversion=1.31
  27. Affected versionversion=1.32
  28. Affected versionversion=1.33
  29. Affected versionversion=1.34
  30. Affected versionversion=1.35
  31. Affected versionversion=1.36
  32. Affected versionversion=1.37
  33. Affected versionversion=1.38
  34. Affected versionversion=1.39
  35. Affected versionversion=1.4
  36. Affected versionversion=1.40
  37. Affected versionversion=1.41
  38. Affected versionversion=1.42
  39. Affected versionversion=1.43
  40. Affected versionversion=1.44
  41. Affected versionversion=1.45
  42. Affected versionversion=1.46
  43. Affected versionversion=1.47
  44. Affected versionversion=1.5
  45. Affected versionversion=1.6
  46. Affected versionversion=1.7
  47. Affected versionversion=1.8
  48. Affected versionversion=1.9

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Tozed Kangwei Tech Co., Ltd. · ZLT M30Sversion=1.0; version=1.1; version=1.10; version=1.11; version=1.12; version=1.13; version=1.14; version=1.15; version=1.16; version=1.17; version=1.18; version=1.19; version=1.2; version=1.20; version=1.21; version=1.22; version=1.23; version=1.24; version=1.25; version=1.26; version=1.27; version=1.28; version=1.29; version=1.3; version=1.30; version=1.31; version=1.32; version=1.33; version=1.34; version=1.35; version=1.36; version=1.37; version=1.38; version=1.39; version=1.4; version=1.40; version=1.41; version=1.42; version=1.43; version=1.44; version=1.45; version=1.46; version=1.47; version=1.5; version=1.6; version=1.7; version=1.8; version=1.9

Published CVSS scores

2.0VulDBCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.6NIST NVDCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
0.3VulDBCVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
1.2VulDBAV:L/AC:H/Au:N/C:P/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-1191On-Chip Debug and Test Interface With Improper Access Control
T1552Unsecured Credentials

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo