CVE-2025-53842VulnerabilityPublished 16 Jul 2025Updated 18 Jul 2025

CVE-2025-53842: ZEXELON ZWX-2000CSW2-HN · Use of hard-coded credentials

Affects ZEXELON ZWX-2000CSW2-HNSource CVE Database V5

Mentioned vulnerabilities

CVE-2024-39838

Not known to be exploited · CVSS 4.5 Medium : upgrade to 0.3.19 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

4.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.3.19

CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ZEXELON ZWX-2000CSW2-HN to 0.3.19.

Affected software

Product	Affected	Fixed in
ZEXELON CO., LTD. ZWX-2000CSW2-HN	Affected <0.3.19	Fixed in 0.3.19

AI-suggested

Given the absence of official patches, European organizations should implement specific mitigations: 1) Network Segmentation: Isolate affected devices on dedicated network segments with strict access controls to limit exposure to only trusted administrators. 2) Access Control Hardening: Enforce strong authentication mechanisms for device management interfaces and restrict administrative access to known, secure endpoints. 3) Credential Management: Replace or disable hard-coded credentials where possible by updating device configurations or applying vendor-provided workarounds. 4) Monitoring and Logging: Implement enhanced monitoring of device management traffic and log all administrative access attempts to detect suspicious activities promptly. 6) Incident Response Preparedness: Develop and test incident response plans specific to device compromise scenarios to minimize impact if exploitation occurs. 7) Vendor Engagement: Engage with ZEXELON to confirm the status of fixes and request detailed guidance on remediation steps.

Description

Use of hard-coded credentials issue exists in ZWX-2000CSW2-HN prior to 0.3.19 and ZWX-2000CS2-HN firmware all versions. If this vulnerability is exploited, an attacker may tamper with the settings of the device by obtaining the credentials. This vulnerability is caused by an insufficient fix for CVE-2024-39838.

Impact

For European organizations, the exploitation of this vulnerability could lead to unauthorized access and manipulation of network devices, potentially compromising network integrity and confidentiality. Since the vulnerability allows attackers to obtain hard-coded credentials, it could facilitate lateral movement within internal networks, especially in environments where these devices serve as critical infrastructure components such as network switches or controllers. The confidentiality impact is high, as attackers can extract sensitive credentials, but integrity and availability impacts are not directly affected by this vulnerability. However, indirect impacts such as misconfiguration or network disruption could occur if attackers modify device settings. This risk is particularly relevant for sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, where unauthorized access could lead to data breaches or operational disruptions. The requirement for high privileges and adjacent network access somewhat limits remote exploitation, but insider threats or compromised internal systems could leverage this vulnerability effectively.

References

Community reviews

Loading reviews…