CVE-2026-30704
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-30704 is a critical-severity Hidden Functionality (CWE-912) vulnerability in Github (inferred from references). Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30704 is a high-severity vulnerability (CVSS v3.1 score of 9.1, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H) affecting the WiFi Extender WDR201A, specifically hardware version V2.1 running firmware LFMZX28040922V1.02. The issue stems from the exposure of an unprotected UART interface via accessible hardware pads on the device's printed circuit board (PCB), classified under CWE-912 (Hidden Functionality). This allows unauthorized access to potentially sensitive hardware-level interfaces.
An attacker with the ability to exploit this vulnerability, as indicated by the CVSS metrics, can do so remotely over the network (AV:N) with low attack complexity (AC:L), no required privileges (PR:N), and no user interaction (UI:N). Successful exploitation enables high-impact compromise of confidentiality (C:H) and availability (A:H), such as extracting sensitive data or disrupting device operations through the UART interface, while integrity remains unaffected (I:N) under an unchanged scope (S:U).
Advisories reference a detailed security research disclosure at https://mstreet97.github.io/security-research/iot/vulnerability-disclosure/cybersecurity/cve/2026/02/18/From-Blackbox-to-Whitebox-Multiple-CVEs-in-a-Consumer-WiFi-Extender.html, which covers this and other CVEs in the device, alongside manufacturer information for Yeapook (https://www.made-in-china.com/showroom/yeapook/#:~:text=Established%20in%202015.%2CDistrict%2C%20Shenzhen%2C%20Guangdong%2C%20China), a Shenzhen-based producer established in 2015; no specific patches or mitigations are detailed in the provided references.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12878
Vulnerability Data
The WiFi Extender WDR201A (HW V2.1, FW LFMZX28040922V1.02) exposes an unprotected UART interface through accessible hardware pads on the PCB
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.
Application security requirements explicitly define expected functionality, making hidden features a violation.
Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.