dbcve.org
Wl Wn578w2 FirmwareOperating system · Wavlink

CVE-2025-10358

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 security vulnerability has been detected in Wavlink WL-WN578W2 221110. This affects the function sub_404850 of the file /cgi-bin/wireless.cgi. The manipulation of the argument delete_list leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed publicly 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 wireless router firmware. The 'delete_list' parameter passed to the sub_404850 function in /cgi-bin/wireless.cgi is not properly sanitized before being used in shell command execution, allowing remote attackers to inject arbitrary OS commands with root privileges.

MitigationSince the vendor has not responded to the disclosure, immediate mitigations include restricting network access to the device's web interface via firewall rules or VLAN segmentation, disabling the wireless.cgi endpoint if possible, or replacing the device with a supported model from a vendor that provides security patches.

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 device model
    Access the router web interface or check the device label to confirm it is a Wavlink WL-WN578W2 model
    Affected if The device is not a Wavlink WL-WN578W2
  2. Check firmware version
    Log into the router web interface and navigate to the Administration or System settings page to view the firmware version. Alternatively, check the version string in the bootloader or through telnet/ssh access if available.
    Affected if Firmware version is m78w2_v221110 exactly
  3. Verify web interface accessibility
    Attempt to access http://[router-ip]/cgi-bin/wireless.cgi from a browser to confirm the endpoint is reachable
    Affected if The wireless.cgi endpoint responds and is accessible from the network
  4. Assess network exposure
    Check if the router web interface (port 80/443) is exposed to the internet or untrusted networks. Review firewall rules and port forwarding configurations.
    Affected if The router web interface is accessible from untrusted networks or the internet

A user is affected if they have a Wavlink WL-WN578W2 router running firmware version m78w2_v221110 with the wireless.cgi endpoint accessible from their network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not responded to the disclosure, immediate mitigations include restricting network access to the device's web interface via firewall rules or VLAN segmentation, disabling the wireless.cgi endpoint if possible, or replacing the device with a supported model from a vendor that provides security patches.

Recommended fix Low confidence
  1. Isolate the affected device on a restricted network segment to limit exposure to remote attacks
  2. Restrict access to the device's web management interface (port 80/443) to trusted IPs only, ideally through firewall rules
  3. If the device's web interface is not required for regular operation, disable remote management and use only local access
  4. Contact Wavlink support again to inquire about firmware security updates, documenting the CVE reference
  5. Consider replacing the device with a model that actively maintains firmware security updates
  6. Monitor vendor announcements for any future security patches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wl Wn578w2 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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