CVE-2026-41922
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 · uneditedWDR201A WiFi Extender (HW V2.1, FW LFMZX28040922V1.02) contains an OS command injection vulnerability in the wireless.cgi binary that allows unauthenticated remote attackers to execute arbitrary shell commands by injecting malicious input into the sz11gChannel or PIN POST parameters. Attackers can exploit unsanitized parameter handling in the set_wifi_basic and set_wifi_do_wps functions to achieve remote code execution without authentication.
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 confidenceOS command injection vulnerability in the wireless.cgi binary of WDR201A WiFi Extender firmware LFMZX28040922V1.02 allows unauthenticated remote attackers to execute arbitrary shell commands via unsanitized sz11gChannel or PIN POST parameters in the set_wifi_basic and set_wifi_do_wps functions, achieving unauthenticated remote code execution.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 is WDR201A WiFi ExtenderAccess the device web interface or check the device label/marketing to identify the exact model numberAffected if Device model is WDR201A WiFi Extender
-
Identify installed firmware versionLog into the device web interface and navigate to the status or system settings page to view the firmware version, or use SNMP or telnet/SSH to query the device if availableAffected if Firmware version matches LFMZX28040922V1.02 or is an earlier version of this firmware line
-
Verify wireless.cgi endpoint is accessibleAttempt to access http://device-ip/cgi-bin/wireless.cgi or similar path common for this device's web interface to confirm the binary exists and responds to requestsAffected if The wireless.cgi binary is accessible and responds to HTTP requests on the device
-
Check if WPS functionality is enabledLog into the device web interface and navigate to wireless settings to determine whether Wi-Fi Protected Setup (WPS) is currently enabled or disabledAffected if WPS is enabled on the device (since set_wifi_do_wps function is listed as affected)
-
Confirm web management interface is network-exposedVerify whether the device web interface is accessible from untrusted networks (not behind a firewall or VPN) by checking network configuration and exposureAffected if The device web interface is directly exposed to untrusted networks without authentication barriers
The device is affected if it is a WDR201A WiFi Extender running firmware LFMZX28040922V1.02 or earlier, with the wireless.cgi binary accessible and WPS or wireless basic settings exposed via the web interface to untrusted networks.
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 dataImmediately restrict network exposure of affected devices or disable WPS functionality; contact vendor for patched firmware; if no patch available, isolate or replace the device.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41922 — 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-41922 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