dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4164

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
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
A flaw has been found in Wavlink WL-WN578W2 221110. Impacted is the function Delete_Mac_list/SetName/GuestWifi of the file /cgi-bin/wireless.cgi of the component POST Request Handler. Executing a manipulation can lead to command injection. It is possible to launch the attack remotely. The exploit has been published and may be used. It is recommended to upgrade the affected component.

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

A command injection vulnerability exists in the Wavlink WL-WN578W2 router firmware (221110) within the /cgi-bin/wireless.cgi script. The POST request handler functions Delete_Mac_list, SetName, and GuestWifi fail to properly sanitize input, allowing remote attackers to inject arbitrary OS commands with root privileges.

MitigationUpgrade the Wavlink WL-WN578W2 firmware to the latest version from the vendor; if no patch is available, disable the affected wireless management functions externally or place the device behind a filtered gateway.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify device model and firmware version
    Access the router web interface or check the device label/metadata. Look for the firmware version displayed in the admin panel (typically under System or Administration settings). For CLI access, check /etc/version or the output of 'nvram show' if available.
    Affected if The device is a Wavlink WL-WN578W2 running firmware version 221110 or other unpatched versions.
  2. Confirm wireless.cgi endpoint accessibility
    Attempt to reach the router's /cgi-bin/wireless.cgi endpoint via HTTP/HTTPS from an authenticated session or from the local network. Use a tool like curl: curl -k http://<router-ip>/cgi-bin/wireless.cgi
    Affected if The endpoint responds with any HTTP status (200, 401, etc.) indicating the script exists and is reachable.
  3. Verify wireless management functions are enabled
    Check the router's wireless settings page in the web interface. Look for MAC filtering (used by Delete_Mac_list), wireless network name settings (used by SetName), and guest WiFi configuration (used by GuestWifi). These features are typically found under Wireless or Advanced Wireless settings.
    Affected if Any of these wireless management features (MAC filtering, custom SSID settings, or guest WiFi) are enabled in the router configuration.
  4. Check for unauthenticated or weak authentication exposure
    Review whether the wireless.cgi endpoint requires authentication. Test if the vulnerable functions can be accessed with default credentials (admin/admin is common on Wavlink devices) or without authentication.
    Affected if The wireless.cgi script or its functions (Delete_Mac_list, SetName, GuestWifi) can be reached with default credentials or without valid authentication.

If the device is a Wavlink WL-WN578W2 with firmware version 221110, the wireless.cgi endpoint is accessible, and wireless management features are enabled, the device is likely vulnerable to command injection via the affected functions.

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

Upgrade the Wavlink WL-WN578W2 firmware to the latest version from the vendor; if no patch is available, disable the affected wireless management functions externally or place the device behind a filtered gateway.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4164 — 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-4164 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