CVE-2026-30701
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 web interface of the WiFi Extender WDR201A (HW V2.1, FW LFMZX28040922V1.02) contains hardcoded credential disclosure mechanisms (in the form of Server Side Include) within multiple server-side web pages, including login.shtml and settings.shtml. These pages embed server-side execution directives that dynamically retrieve and expose the web administration password from non-volatile memory at runtime.
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 WDR201A WiFi Extender firmware (V1.02) contains a hardcoded credential disclosure vulnerability where Server Side Include (SSI) directives embedded in login.shtml and settings.shtml dynamically retrieve and expose the web administration password from non-volatile memory at runtime. An attacker with network access to the web interface can extract these credentials to gain full administrative access to the device.
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.
-
Confirm device model and firmware versionAccess the device administration interface or check the device label/management console to identify if the device is a WDR201A WiFi Extender running firmware version V1.02Affected if The device is a WDR201A WiFi Extender running firmware V1.02
-
Verify web interface is network-accessibleDetermine if the device web administration interface is reachable over the network from an attacker perspective (not just from within the local LAN or with authentication)Affected if The web management interface is exposed to network access without adequate access controls
-
Inspect login.shtml for credential disclosureLocate and examine the login.shtml file on the device firmware or via the live web interface for SSI directives that dynamically retrieve the administrative password from non-volatile memoryAffected if The login.shtml file contains SSI directives that expose the web administration password at runtime
-
Inspect settings.shtml for credential disclosureLocate and examine the settings.shtml file on the device firmware or via the live web interface for SSI directives that dynamically retrieve the administrative password from non-volatile memoryAffected if The settings.shtml file contains SSI directives that expose the web administration password at runtime
The device is affected if it is a WDR201A WiFi Extender running firmware V1.02 with its web interface network-accessible and the login.shtml or settings.shtml files contain SSI directives that expose the administrative password from memory.
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 dataContact the vendor for a firmware patch that removes the hardcoded credential disclosure mechanism. If no patch is available, replace the device and implement network segmentation to restrict access to the management interface.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30701 — 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-30701 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