Zbtlink L3_V2_8 firmware 3.0.0.4.528, Zbtlink WE826-T2 firmware 19.1101, Zbtlink ZBT-7628 firmware 1.0.0.2.007, Zbtlink ZBT-ZBT7621 firmware 1.0.0.3.001, MoreQuick MQAC-7620, MQAC-7620A, MQAP-7620, MQAP-7620A, and MQAP-7628 firmware 1.0.0.2.000, AP522 firmware 1.0.0.2.014, AP7628 and HC5661A firmware 3.0.0.4.380, APG721B firmware 19.0809, HK300 firmware 1.0.0.2.032, and MAP-N10 firmware 1.0.0.2.044 ship a backdoor command-and-control implant (yunmgrd) reachable over an unauthenticated cleartext UDP channel to a hardcoded C2 server. A remote unauthenticated attacker on the network path can hijack the channel and execute arbitrary commands as root. The attacker can also modify DNS entries, exfiltrate PPPoE credentials, and open reverse SSH tunnels.
Security readout for executives and security teams
Plain-English summary
Affected routers and access points contain a built-in cloud management implant that communicates without authentication or encryption. An attacker able to intercept that network traffic could take full control as root, alter DNS, steal internet credentials, or establish remote access. This creates severe confidentiality, integrity, and availability risk.
Executive priority
Treat confirmed affected devices as an immediate remediation priority, especially at internet gateways or sensitive sites. Isolate and assess them promptly because compromise could redirect traffic, expose connectivity credentials, and provide persistent root access. No patch or vendor-supported fix is identified in the supplied sources, so replacement planning may be necessary.
Technical view
The yunmgrd component uses an unauthenticated cleartext UDP channel to a hardcoded command-and-control server. A network-path attacker can hijack this channel and execute arbitrary commands as root. Reported additional impacts include DNS modification, PPPoE credential exfiltration, and reverse SSH tunnels. The CVE maps to CWE-300 and CWE-506 and carries CVSS 3.1 score 9.8.
Likely exposure
Exposure is limited to the listed Zbtlink, MoreQuick, and unidentified-brand device models running the exact reported firmware versions. Risk depends on whether yunmgrd is active and its UDP traffic can reach or traverse attacker-observable networks. The sources provide no CPE mappings, deployment prevalence, or confirmed unaffected versions.
Exploitation context
The attack requires no device credentials or user interaction but does require access to the management channel's network path. The supplied record is not in KEV, and the cited material does not establish active exploitation. The implant's root-level command capability and cleartext unauthenticated transport nevertheless make successful compromise highly consequential.
Researcher notes
The record names 15 products and exact firmware builds, including devices whose vendor is unidentified. Evidence supports a deliberately included yunmgrd implant and network-path channel hijacking, but does not document exploitation in the wild, the hardcoded server address, patch availability, or broader version ranges. Avoid extrapolating exposure beyond the enumerated builds without additional firmware analysis.
Mitigation direction
Identify and isolate devices matching the listed models and firmware versions.
Restrict unnecessary outbound UDP and management traffic from affected network devices.
Check vendor guidance for corrected firmware, replacement, or supported mitigation instructions.
After suspected compromise, rotate exposed PPPoE credentials and review DNS settings.
Replace affected devices if no trustworthy vendor remediation becomes available.
Validation and detection
Record each device model, firmware version, vendor identity, and network location.
Determine whether yunmgrd is present, running, or configured to start automatically.
Review network telemetry for unexpected UDP communication associated with affected devices.
Inspect DNS configuration for unauthorized changes and look for unexplained SSH tunnels.
Check whether PPPoE credentials may have been exposed, then investigate related account activity.
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-300: 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.
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.
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.
2CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-300 · source CWE mapping
Channel Accessible by Non-Endpoint
Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.