High Info disclosure exploit reference

CVE-2025-15082 — TOZED ZLT M30s Web Management proc_post information disclosure

A vulnerability was found in TOZED ZLT M30s up to 1.47. Impacted is an unknown function of the file /reqproc/proc_post of the component Web Management Interface. Performing manipulation of the argument goformId results in information disclosure. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Published Dec 25, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.7% (30-day exploitation probability)+8
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.7%

ahead of 52% of scored CVEs · Oct 14, 2026

Affects

Gztozed

Zlt M30s Firmware and 1 more

CVSS base

7.5

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Gztozed Zlt M30s Firmware, TOZED ZLT M30S).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Gztozed	Zlt M30s Firmware	≤ 1.47	Vulnerable	NIST National Vulnerability Database
TOZED	ZLT M30S	version 1.36version 1.25version 1.26version 1.27version 1.28version 1.29version 1.30version 1.31 and 40 more version 1.32version 1.33version 1.34version 1.35version 1.23version 1.37version 1.38version 1.39version 1.40version 1.41version 1.42version 1.43version 1.44version 1.45version 1.46version 1.47version 1.11version 1.0version 1.1version 1.2version 1.3version 1.4version 1.5version 1.6version 1.7version 1.8version 1.9version 1.10version 1.24version 1.12version 1.13version 1.14version 1.15version 1.16version 1.17version 1.18version 1.19version 1.20version 1.21version 1.22	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.9	CVSS 4.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
5.5	CVSS 4.0	Medium	—	—	cna@vuldb.com via NIST National Vulnerability Database
7.5	CVSS 3.1	High	3.9	3.6	nvd@nist.gov via NIST National Vulnerability Database
5.3	CVSS 3.1	Medium	3.9	1.4	cna@vuldb.com via NIST National Vulnerability Database
5.3	CVSS 3.1	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
5.3	CVSS 3.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
5.0	CVSS 2.0	Medium	10.0	2.9	cna@vuldb.com via NIST National Vulnerability Database
5.0	CVSS 2.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.5 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.70%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for anomalous data read/export volumes and access to sensitive records.

web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · tozed/zlt m30s
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Dec 25, 2025 · VulDB

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

vuldb.com/
Third Party Advisory, VDB Entry, third-party-advisory, NIST National Vulnerability Database
vuldb.com/
Third Party Advisory, VDB Entry, vdb-entry, technical-description, NIST National Vulnerability Database
www.hacklab.eu.org/blogs/zlt_m30s_information_disclosure
Exploit, Third Party Advisory, related, NIST National Vulnerability Database
vuldb.com/
Permissions Required, VDB Entry, signature, permissions-required, NIST National Vulnerability Database
youtu.be/u_H29UdiPOc
Exploit, exploit, media-coverage, NIST National Vulnerability Database

Elsewhere on this site

Gztozed
every CVE for this vendor

Info disclosure
same class

CWE-200
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2025-15083 TOZED ZLT M30s UART on-chip debug and test interface with improper access control Dec 25, 2025
High CVE-2025-14126 TOZED ZLT M30S/ZLT M30S PRO Web hard-coded credentials Dec 6, 2025
Medium CVE-2025-14105 TOZED ZLT M30S/ZLT M30S PRO Web proc_post denial of service Dec 5, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-15082 is "TOZED ZLT M30s Web Management proc_post information disclosure", rated High. It affects Zlt M30s Firmware (Gztozed); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.70% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.