dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-41924

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
WDR201A WiFi Extender (HW V2.1, FW LFMZX28040922V1.02) contains an OS command injection vulnerability in the makeRequest.cgi binary that allows unauthenticated remote attackers to execute arbitrary shell commands by injecting malicious input into the set_time or StartSniffer functions. Attackers can craft a POST request with specially crafted ampersand-delimited parameters to bypass input sanitization and execute commands with a maximum length of 31 bytes through the date command or channel parameter processing.

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 confidence

OS command injection vulnerability in WDR201A WiFi Extender's makeRequest.cgi binary allows unauthenticated remote attackers to execute arbitrary shell commands via specially crafted POST requests to the set_time or StartSniffer functions. The attack uses ampersand-delimited parameters to bypass input sanitization, with command execution limited to 31 bytes through the date command or channel parameter processing.

MitigationApply vendor firmware patch when available; until then, network-segment the device behind a firewall to limit exposure to untrusted networks and consider disabling the affected CGI endpoints if functionality permits.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the device label, web interface footer, or SNMP/sysinfo for the exact model number (WDR201A WiFi Extender). If unsure, compare the web UI login page against known WDR201A screenshots or check the MAC address OUI against the vendor.
    Affected if The device is not a WDR201A WiFi Extender (different model or manufacturer).
  2. Verify makeRequest.cgi is accessible
    Attempt to access the CGI endpoint via HTTP/HTTPS (e.g., https://<device-ip>/makeRequest.cgi). A 200 OK response or the CGI returning any output indicates the interface is present.
    Affected if The CGI returns 404 or is unreachable (the vulnerability only applies if the CGI exists and is reachable).
  3. Confirm remote CGI access is enabled
    Check the device administration settings for remote web management. If the web UI is accessible from WAN/outside the local network, the attack surface is present. Verify if the set_time and StartSniffer functions are listed in the CGI or available via help pages.
    Affected if Remote CGI access is disabled and the device is only manageable from the local LAN, reducing exposure to unauthenticated remote attackers.
  4. Check for the vulnerable parameter handling
    Inspect any captured traffic or device logs for POST requests to set_time or StartSniffer functions. Review the CGI parameters accepted - the vulnerability uses ampersand-delimited parameter injection.
    Affected if The device firmware has already patched the parameter parsing or removed these functions entirely.

You are affected if you have a WDR201A WiFi Extender with the makeRequest.cgi interface accessible remotely and the set_time/StartSniffer functions are present in the firmware.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; until then, network-segment the device behind a firewall to limit exposure to untrusted networks and consider disabling the affected CGI endpoints if functionality permits.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41924 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41924 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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