CVE-2023-50614VulnerabilityPublished 18 Jan 2024Updated 2 Jun 2025

CVE-2023-50614: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 18 Jan 2024
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

AI-suggested

1. Network Segmentation: Isolate EBYTE E880-IR01-V1.1 devices from public internet access and restrict access to trusted management networks only. 2. Access Controls: Implement strict firewall rules to block unauthorized access to the /cgi-bin/luci endpoint and monitor for unusual POST requests targeting this path. 3. Device Hardening: Disable or restrict web management interfaces if not required, or configure them to require strong authentication and encrypted communication channels (e.g., HTTPS). 4. Monitoring and Detection: Deploy intrusion detection systems (IDS) and log analysis to identify attempts to exploit this vulnerability by detecting anomalous POST requests to the vulnerable endpoint. 5. Vendor Engagement: Engage with EBYTE or authorized distributors to obtain security patches or firmware updates addressing this vulnerability. 6. Incident Response Preparation: Prepare to respond to potential data leakage incidents by having clear procedures for containment, investigation, and notification in compliance with GDPR and other regulations. 7. Regular Audits: Conduct periodic security assessments of IoT and embedded devices to identify similar vulnerabilities and ensure compliance with security policies.

Description

An issue discovereed in EBYTE E880-IR01-V1.1 allows an attacker to obtain sensitive information via crafted POST request to /cgi-bin/luci.

Impact

For European organizations, the impact of CVE-2023-50614 could be substantial, especially for those relying on EBYTE E880-IR01-V1.1 devices in their network infrastructure or IoT deployments. The exposure of sensitive information could lead to the compromise of confidential data, potentially including network configuration, credentials, or other critical operational details. This leakage could facilitate further attacks such as network intrusion, lateral movement, or espionage. Since the vulnerability does not affect integrity or availability directly, the immediate operational disruption risk is lower; however, the confidentiality breach alone can have severe consequences including regulatory non-compliance under GDPR, reputational damage, and financial loss. Organizations in sectors with high security requirements such as critical infrastructure, manufacturing, or telecommunications may be particularly vulnerable. The remote and unauthenticated nature of the exploit increases the risk of widespread scanning and exploitation attempts, especially if these devices are exposed to the internet or poorly segmented internal networks.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/cvdyfbwa/Password-plaintext-output/blob/main/README.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Jul 2025, 17:02 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats