dbcve.org
Wl Wn578w2 FirmwareOperating system · Wavlink

CVE-2025-10359

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-13
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
Public exploit 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 vulnerability was detected in Wavlink WL-WN578W2 221110. This impacts the function sub_404DBC of the file /cgi-bin/wireless.cgi. The manipulation of the argument macAddr results in os command injection. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 Wavlink WL-WN578W2 router firmware (version 221110). The wireless.cgi script fails to sanitize the macAddr parameter before passing it to system commands, allowing remote attackers to execute arbitrary operating system commands with elevated privileges.

MitigationSince the vendor has not responded and no patch is available, immediately restrict administrative access to the device through firewall rules or network isolation (VPN/bypass admin interface from untrusted networks). Monitor for indicators of compromise. Consider replacing the device if network isolation is not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wl Wn578w2 FirmwareOperating system
Affected:= m78w2_v221110

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 the router model
    Access the router web interface (typically at 192.168.1.1 or 192.168.10.1) and look for the device model in the status or system information page. Alternatively, check the label on the device or access via SSH/Telnet and run 'cat /proc/cpuinfo' or 'nvram get model'
    Affected if The device model is Wavlink WL-WN578W2
  2. Check the firmware version
    In the router web interface, navigate to Administration > Firmware Upgrade or System > Status to find the firmware version. The exact version string is 'm78w2_v221110'. If accessing via CLI, check '/etc/version' or run 'nvram get firmware_version'
    Affected if The firmware version is exactly m78w2_v221110
  3. Verify wireless.cgi is present
    If you have CLI access, check for the existence of the wireless.cgi script. Common paths include '/www/cgi-bin/wireless.cgi' or check within the web server root. Attempt to access the URL 'http://[router-ip]/cgi-bin/wireless.cgi' via curl or browser
    Affected if The wireless.cgi script exists and is accessible on the device
  4. Determine web interface network exposure
    Check your firewall or router configuration to see if the administrative web interface (port 80/443) is exposed to WAN/internet. Run 'netstat -tlnp | grep -E ':(80|443)' or review port forwarding rules. Confirm remote management is disabled in the admin panel under Administration > Remote Management
    Affected if The router web interface is accessible from WAN/internet or remote management is enabled
  5. Look for indicators of compromise
    Check for unexpected processes or network connections. Run 'ps' to list running processes and look for unknown binaries. Review '/tmp' and '/var' directories for suspicious files. Check system logs in /var/log/ for any unexpected command execution or authentication events
    Affected if Unexpected processes, suspicious files in /tmp, or anomalous log entries showing command execution are found

You are affected if the device is a Wavlink WL-WN578W2 running firmware version m78w2_v221110 with the wireless.cgi script present and the web interface exposed to network attackers.

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

Since the vendor has not responded and no patch is available, immediately restrict administrative access to the device through firewall rules or network isolation (VPN/bypass admin interface from untrusted networks). Monitor for indicators of compromise. Consider replacing the device if network isolation is not feasible.

Fix this in Wl Wn578w2 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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