LiveActive security incident?Get immediate response
CVE Record

CVE-2026-19901: LB-LINK X-PRO easycwmp hard-coded credentials

A security flaw has been discovered in LB-LINK X-PRO 1.0.22-20231206. This affects an unknown function of the file /etc/config/easycwmp. The manipulation results in hard-coded credentials. It is possible to launch the attack remotely. Attacks of this nature are highly complex. The exploitability is reported as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

LB-LINK X-PRO firmware 1.0.22-20231206 contains built-in credentials for its easycwmp remote-management component. An attacker who can reach the affected service may gain substantial control without possessing unique device credentials. The published severity is critical, although exploitation is described as difficult.

Executive priority

Treat as an urgent containment and inventory issue, especially for internet-accessible or remotely managed devices. Because public exploit material exists and no confirmed vendor fix is cited, prioritize exposure reduction and consider replacement where isolation is impractical.

Technical view

Hard-coded credentials are present in /etc/config/easycwmp, associated with TR-069 remote management. The issue is remotely reachable, requires no privileges or user interaction, and may compromise confidentiality, integrity, and availability. CVSS 4.0 rates it 9.2, with high attack complexity.

Likely exposure

Exposure is limited by the available evidence to LB-LINK X-PRO version 1.0.22-20231206. Risk is greatest where easycwmp remote management is enabled and reachable from untrusted networks. The bundle does not establish whether other firmware versions or models are affected.

Exploitation context

Public exploit information is available, increasing practical risk. However, the attack is reportedly complex and difficult. The CVE is not listed as CISA KEV in the supplied bundle, and no cited source establishes active exploitation in the wild.

Researcher notes

The assessment relies on third-party reporting and a public disclosure rather than a responsive vendor advisory. Product naming varies between X-PRO and B-Link AC1200 X-PRO in the supplied references. Scope should therefore remain confined to the stated firmware until independently confirmed.

Mitigation direction

  • Identify and prioritize all X-PRO devices running firmware 1.0.22-20231206.
  • Disable easycwmp or restrict remote-management access to trusted management networks.
  • Check LB-LINK guidance for corrected firmware; no confirmed patch is named in the sources.
  • Replace or isolate affected devices if no vendor-supported remediation is available.
  • Rotate related management credentials after containment and investigate suspected unauthorized access.

Validation and detection

  • Verify device models and exact firmware versions against asset and configuration records.
  • Securely inspect affected devices for hard-coded credentials in the easycwmp configuration.
  • Confirm easycwmp is disabled or unreachable from untrusted networks.
  • Review remote-management logs for unusual access, configuration changes, or unexpected endpoints.
  • After remediation, confirm the vulnerable firmware or exposed service is no longer present.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-259: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cwe · medium confidence lookup

CWE-798: 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 lookup
cve · low confidence lookup

CVE-2026-19901 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Official CVE source material

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.

4CVSS vectors
6Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

4 official scores

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——VulDB
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.25.9VulDB
8.1CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.25.9VulDB
7.6CVSS 2.0HighAV:N/AC:H/Au:N/C:C/I:C/A:C/E:POC/RL:ND/RC:UR4.910VulDB

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-19901Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LB-LINKX-PRO1.0.22-20231206Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-259 · source CWE mapping

Use of Hard-coded Password

Use of Hard-coded Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-798 · source CWE mapping

Use of Hard-coded Credentials

Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.