Skip to main content
VulnerabilityPublished

CVE-2026-24789: ZLAN Information Technology Co ZLAN5143D · Missing Authentication

Affects ZLAN Information Technology Co ZLAN5143DSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ZLAN Information Technology Co.ZLAN5143DAffected
  • =1.600
Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Immediately isolate ZLAN5143D devices from untrusted networks, restricting management interfaces to trusted internal segments only. 2) Employ network segmentation and firewall rules to limit access to the vulnerable API endpoint, allowing only authorized management hosts. 3) Monitor network traffic for unusual API calls or password change attempts targeting ZLAN5143D devices. 4) Conduct regular audits of device configurations and access logs to detect unauthorized changes. 5) Engage with the vendor to obtain timelines for patches or firmware updates and request interim security guidance. 6) Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures tailored to detect exploitation attempts. 7) If feasible, replace vulnerable devices with alternative products that have robust authentication controls. 8) Educate IT and security teams about the vulnerability and ensure incident response plans include scenarios involving device compromise. These measures go beyond generic advice by focusing on network-level controls and proactive monitoring tailored to the specific vulnerability context.

Description

An unprotected API endpoint allows an attacker to remotely change the device password without providing authentication.

References

Community reviews

Loading reviews…