Security readout for executives and security teams
Plain-English summary
Xiiaozet LK100W devices may expose a management function without requiring authentication. A remote attacker could enable restricted administrative services and potentially gain unauthorized device access. Because exploitation requires no privileges or user interaction and may affect confidentiality, integrity, and availability, exposed devices warrant urgent review.
Executive priority
Treat confirmed affected or externally reachable devices as an immediate remediation priority. Direct owners to isolate management access, verify versions, and obtain current vendor guidance. Prioritize monitoring where patch information is unavailable. The urgency derives from potential unauthenticated remote compromise, not evidence of active exploitation.
Technical view
CVE-2026-78239 is a CWE-306 missing-authentication flaw affecting listed Xiiaozet LK100W versions 0 and 2.1.240. The vulnerable management function is remotely reachable under the CVSS assessment and can enable administrative services without authentication. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges, no user interaction, and high impact across confidentiality, integrity, and availability.
Likely exposure
Highest risk applies where an affected LK100W management interface is reachable from untrusted networks. Internal-only devices remain exposed to attackers with network access. The supplied data lists versions 0 and 2.1.240, while default status is unaffected; confirm exact firmware and applicability against CISA or vendor guidance.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not listed as KEV. Nevertheless, the stated network accessibility, low complexity, and absence of authentication make reachable affected devices attractive targets. No exploit method or proof-of-concept is established by the supplied evidence.
Researcher notes
The core issue is CWE-306: authentication is missing for a critical function that enables administrative services. The supplied CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Evidence does not identify the protocol, endpoint, default exposure, proof-of-concept availability, vendor fix, or exploitation telemetry; those details should not be inferred.
Mitigation direction
- Inventory Xiiaozet LK100W devices and record their exact firmware versions.
- Remove management interfaces from internet exposure and restrict access to trusted administrative networks.
- Disable unnecessary administrative services where operationally safe.
- Check CISA and Xiiaozet guidance for an approved update or product-specific mitigation.
- Monitor affected network segments for unexpected management access or service changes.
Validation and detection
- Confirm each discovered device model and firmware version against the advisory's affected-product data.
- Verify management interfaces are unreachable from the internet and untrusted network segments.
- Review configuration for unexpectedly enabled administrative services.
- Review device and network logs for unauthorized management connections or unexplained configuration changes.
- After remediation, retest access controls without attempting destructive or exploitative actions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-78239 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9icscertCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——icscertVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-239-01CVE reference, icscert
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-239-01.jsonCVE reference, icscert
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.