CVE-2026-30704
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WiFi Extender WDR201A (HW V2.1, FW LFMZX28040922V1.02) exposes an unprotected UART interface through accessible hardware pads on the PCB
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WiFi Extender WDR201A (HW V2.1, FW LFMZX28040922V1.02) exposes an unprotected UART interface through accessible hardware pads on the PCB. This physical vulnerability allows attackers with physical access to connect to the device's serial console, potentially gaining shell access or extracting sensitive data/debug information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionLocate the device label or access the admin interface to confirm the model is WDR201A and firmware version is LFMZX28040922V1.02Affected if The device is a WiFi Extender WDR201A with firmware LFMZX28040922V1.02 or earlier HW V2.1 version
-
Physically inspect PCB for exposed UART padsOpen the device enclosure and visually examine the PCB for exposed metallic pads or pins labeled TX, RX, GND, or similar UART interfaces, typically located near the edge of the circuit boardAffected if Unprotected UART pads are visible and accessible without tools on the PCB surface
-
Test UART interface connectivityConnect a USB-to-serial adapter (configured at common baud rates such as 115200, 57600, 9600) to the suspected UART pads (TX, RX, GND) and power on the device to observe if a console prompt or boot messages appearAffected if The UART interface responds with readable console output or provides shell access without any authentication prompt
-
Verify boot sequence authenticationAttempt to interact with the UART console during device startup to determine if the boot process requires any password, PIN, or authentication before providing shell or configuration accessAffected if The device provides shell or configuration access immediately upon UART connection without requiring any credentials or user interaction
-
Check for physical hardening measuresExamine the UART pads and surrounding PCB area for signs of conformal coating, potting compound, or physical obstruction that would prevent direct access to the interfaceAffected if The UART pads are exposed without protective coating, potting, or physical barriers preventing direct contact
You are affected if your WDR201A device (HW V2.1, FW LFMZX28040922V1.02) has accessible UART pads on the PCB that provide unauthenticated console or shell access when connected with a serial adapter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataPhysical security controls (enclosure locking, tamper-evident seals) should be implemented; additionally, UART console access should be disabled or password-protected in firmware if possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30704 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data