VulnerabilityPublished 4 Nov 2023Updated 4 Nov 2025

CVE-2023-46382: Certain LOYTEC devices, including LINX-151, LINX-212, LVIS-3ME12-A1, LIOB-586, LIOB-580 V2, LIOB-588,

Source CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 2.5% chance of exploitation in 30 days – higher than 84% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2023
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

Since the devices use cleartext HTTP for login, it is recommended to restrict network access to these devices to trusted networks only and use network-level protections such as VPNs or segmentation to reduce exposure. Monitor vendor advisories for any future updates or patches addressing this issue.

Description

Certain LOYTEC devices, including LINX-151, LINX-212, LVIS-3ME12-A1, LIOB-586, LIOB-580 V2, LIOB-588, and L-INX Configurator, use cleartext HTTP for login across all versions. This means that login credentials are transmitted without encryption, potentially exposing them to interception.

Impact

The use of cleartext HTTP for login credentials can lead to credential interception by attackers with network access, potentially allowing unauthorized access to affected devices. This exposure increases the risk of compromise of device management and control, but no specific exploit or active attacks are documented.

Summary

LOYTEC LINX-151, LINX-212, LVIS-3ME12-A1, LIOB-586, LIOB-580 V2, LIOB-588, and L-INX Configurator devices use unencrypted HTTP for login processes in all versions. This vulnerability involves the transmission of authentication credentials in cleartext, which can be intercepted by attackers on the same network or with access to network traffic. No CVSS score or further technical details are provided, and no known exploits in the wild have been reported.

References

Community reviews

Loading reviews…