Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain on-path position to device C2 UDP traffic
-
DeliverySpoof or hijack hardcoded C2 channel
-
ExploitIssue commands to yunmgrd implant
-
ExecutionExecute arbitrary commands as root
-
PersistOpen reverse SSH tunnel and alter DNS
-
ImpactExfiltrate PPPoE credentials and intercept traffic
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Code review, malicious code detection
|
| Exploitation Conditions | The prerequisite is that the device runs the backdoored firmware containing the 'yunmgrd' implant (the specific models/firmware listed), which beacons to a hardcoded C2 over an unauthenticated, unencrypted UDP channel - no authentication, credentials, or user interaction are required (PR:N/UI:N). The concrete limiting factor is attacker network position: exploitation works by hijacking or impersonating the implant's C2 UDP channel, so the attacker must be able to reach, intercept, spoof, or redirect that channel (on-path upstream, shared network segment, or via routing/DNS manipulation) rather than from any arbitrary internet host. No special non-default configuration is needed because the implant ships and runs by default in the affected images. |
| Impact | The signals are strongly aligned toward high real-world risk. The CVSS 4.0 base score of 9.3 with vector AV:N/AC:L/AT:N/PR:N/UI:N and VC:H/VI:H/VA:H reflects an unauthenticated, low-complexity network attack with full confidentiality, integrity, and availability impact, and this is corroborated by the description (root command execution over an unauthenticated cleartext channel). Publicly available exploit code from VulnCheck lowers the barrier to attack, though it must not be conflated with confirmed active exploitation - this CVE is not shown as CISA KEV in the provided data, so any operator running these devices should treat it as urgent even though widespread in-the-wild exploitation is not confirmed here. One caveat worth verifying: the vector implies a purely network-reachable attack (PR:N), but the description frames exploitation as hijacking the outbound C2 UDP channel, which in practice favors an attacker positioned on the network path (upstream ISP, shared segment, or via DNS/route manipulation) rather than any arbitrary internet host - defenders should confirm exact reachability against their topology. EPSS is not provided in the input, so probabilistic exploitation scoring is unavailable and cannot be weighed here. |
| Exploit ScenarioDerived | An attacker positioned on the network path between an affected router and its hardcoded cloud C2 - for example an upstream/ISP-level actor or someone who can spoof or redirect the C2 endpoint - hijacks the unauthenticated cleartext UDP channel and issues commands to the yunmgrd implant. Given AV:N/AC:L/PR:N, no credentials or user interaction are needed; the attacker executes shell commands as root, rewrites DNS to redirect victim traffic, harvests PPPoE credentials, and opens a reverse SSH tunnel for persistent access. Publicly available exploit code from VulnCheck makes reproduction straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
Root-level remote code execution affects a family of Zbtlink, MoreQuick, and related OEM routers/APs (e.g. L3_V2_8 3.0.0.4.528, WE826-T2 19.1101, ZBT-7628, ZBT-ZBT7621, AP522, AP7628, HC5661A, HK300, MAP-N10) that ship a factory backdoor implant named 'yunmgrd' beaconing to a hardcoded cloud C2 over unauthenticated cleartext UDP. Because the channel is unauthenticated and in cleartext, a remote attacker on the network path can hijack it, impersonate the C2, and run arbitrary commands as root - additionally tampering with DNS, stealing PPPoE credentials, and opening reverse SSH tunnels. Reported by VulnCheck with publicly available exploit code; not currently listed in CISA KEV.
RemediationAI
No specific fixed firmware version is identified in the provided data, so 'No vendor-released patch identified at time of analysis' applies - do not assume a clean firmware exists without confirming directly with Zbtlink/MoreQuick and the VulnCheck advisory (https://www.vulncheck.com/advisories/zbtlink-mqwrt-yunmgrd-cloud-c2-implant). Because the malicious behavior is an embedded backdoor daemon (yunmgrd) rather than a configuration flaw, the highest-assurance remediation is to remove the affected devices from service or reflash them with trustworthy third-party firmware (e.g. a clean OpenWrt build) where hardware support allows, accepting the trade-off of losing vendor features/support. As compensating controls until devices are replaced: block and monitor the device's outbound UDP traffic to the hardcoded C2 destination at an upstream firewall (trade-off: the C2 address must be identified from the VulnCheck blog, and a determined implant may fall back); egress-filter these devices to permit only known-necessary destinations; disable/inspect the yunmgrd process and any reverse-SSH listeners if shell access is possible (trade-off: it may respawn on reboot or restore); pin trusted DNS resolvers and monitor for unexpected DNS changes and PPPoE re-authentication given the credential-theft capability; and isolate the devices on a segmented VLAN to limit lateral movement.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 15 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is CWE-506 (Embedded Malicious Code): the affected firmware images intentionally include a management daemon, 'yunmgrd', that functions as a command-and-control implant rather than a legitimate remote-management service. The daemon connects to a hardcoded C2 endpoint over UDP with no authentication and no encryption (cleartext), meaning any party able to observe or inject traffic on the path - or spoof the C2's address - can drive the implant. The affected devices are MIPS-based OpenWrt-derived SOHO routers and access points (Ralink/MediaTek MT7620/MT7628-class platforms, reflected in model names like 7620/7628/7621) produced by Zbtlink and rebranded by MoreQuick and other OEMs, per the CPE set (cpe:2.3:a:zbtlink:*, cpe:2.3:a:morequick:*, cpe:2.3:a:unknown:ap522). Root command execution combined with DNS manipulation and PPPoE credential theft makes these devices a strong pivot point for traffic interception at the network edge.
Know when Ap522 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Unauthenticated network-reachable backdoor giving root command execution (PR:N/UI:N, AC:L) with full C/I/A impact; scope unchanged as impact stays within the device OS.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
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.
Executive ViewAI
A factory-installed backdoor in Zbtlink, MoreQuick, and several OEM router and access point models (including L3_V2_8 3.0.0.4.528, WE826-T2 19.1101, and variants like ZBT-7628, AP522, HC5661A) enables remote attackers to execute arbitrary commands with root privileges without authentication. This vulnerability compromises network infrastructure integrity across any organization using affected models, enabling credential theft, DNS manipulation, and persistent backdoor access. With publicly available exploit code and no vendor patch currently available, organizations face immediate risk of network compromise from attackers anywhere on the network path.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) Network isolation-segment affected devices to a monitored network with restricted outbound access; (2) Access controls-disable remote management interfaces and restrict administrative credentials to authorized personnel only; (3) Traffic monitoring-log all outbound UDP traffic from affected devices to detect C2 beaconing attempts; (4) Firewall rules-limit device communication to essential network services. However, given the factory-installed nature of this backdoor, device replacement is the only fully effective remediation; interim controls should be viewed as temporary risk reduction pending replacement completion.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-66999
GHSA-jgcj-chrm-4hhc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB