dbcve.org
Wl Wn578w2 FirmwareOperating system · Wavlink

CVE-2025-10324

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-12
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 determined in Wavlink WL-WN578W2 221110. This affects the function sub_401C5C of the file firewall.cgi. This manipulation of the argument pingFrmWANFilterEnabled/blockSynFloodEnabled/blockPortScanEnabled/remoteManagementEnabled causes command injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. 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

A command injection vulnerability exists in the Wavlink WL-WN578W2 router's firewall.cgi web interface. Multiple parameters (pingFrmWANFilterEnabled, blockSynFloodEnabled, blockPortScanEnabled, remoteManagementEnabled) are passed to function sub_401C5C without proper input sanitization, allowing an attacker to inject arbitrary shell commands. The vulnerability is remotely exploitable via the web interface.

MitigationRestrict network access to the router's administrative interface to trusted IPs only; the vendor has not provided a patch, so consider network segmentation or replacement with a supported device.

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. Confirm device model and firmware version
    Access the router's web administration interface and navigate to System Settings or Status page to view the firmware version. Alternatively, check the device label or firmware file name for 'm78w2_v221110' or WN578W2 model identification.
    Affected if The firmware version is exactly m78w2_v221110 (221110 release).
  2. Identify WAN-facing exposure of web interface
    Determine if the router's HTTP/HTTPS web interface (port 80/443) is accessible from the WAN/internet by attempting to access the router's public IP from an external network, or by checking port forwarding/NAT rules on the upstream device.
    Affected if The router's web interface is directly accessible from WAN without VPN or firewall restriction.
  3. Check for default or guessable admin credentials
    Attempt to access the router's login page from WAN. If authentication is default (admin/admin) or easily guessable, the device is fully exploitable. Check for forms at /cgi-bin/login.cgi or /cgi-bin/luci/.
    Affected if The login page is reachable from WAN and uses default credentials or no authentication.
  4. Inspect firewall settings page accessibility
    Once authenticated (or if unauthenticated access is possible), attempt to access the firewall configuration page at /cgi-bin/firewall.cgi or navigate to Firewall Settings in the web UI.
    Affected if The firewall.cgi endpoint is accessible and accepts parameters like pingFrmWANFilterEnabled, blockSynFloodEnabled, blockPortScanEnabled, or remoteManagementEnabled.

You are affected if you are running Wavlink WL-WN578W2 firmware version m78w2_v221110 AND the router's web administration interface is exposed to the WAN/internet.

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

Restrict network access to the router's administrative interface to trusted IPs only; the vendor has not provided a patch, so consider network segmentation or replacement with a supported device.

Fix this in Wl Wn578w2 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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