dbcve.org
Wl Wn570ha1 FirmwareOperating system · Wavlink

CVE-2026-7690

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-03
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 weakness has been identified in Wavlink WL-WN570HA1 R70HA1 V1410_221110. This issue affects the function set_sys_adm of the file /cgi-bin/adm.cgi. This manipulation of the argument Username causes command injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Once again the vendors acted very professional and confirms, "that the WN570HA1 firmware version R70HA1 V1410_221110 has been removed from our website." This vulnerability only affects products that are no longer supported by the maintainer.

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

This is a command injection vulnerability in Wavlink WL-WN570HA1 firmware where the set_sys_adm function in /cgi-bin/adm.cgi fails to sanitize the Username parameter before passing it to a system call. An unauthenticated remote attacker can inject arbitrary OS commands with root privileges, achieving full device compromise. The CVSS 9.8 reflects the critical severity of pre-authentication remote code execution on an exposed network interface.

MitigationSince the vendor has removed the firmware and discontinued support for this product with no patch available, the recommended remediation is to decommission and replace the affected device with a currently supported model. If the device must remain in service, implement strict network segmentation and firewall rules to block external access to the administrative CGI interface.

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 Wn570ha1 FirmwareOperating system
Affected:= r70ha1_v1410_221110

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 is Wavlink WL-WN570HA1
    Access the device web interface and check the status or system information page for the exact model name, or check the device label/physical markings
    Affected if The device is a Wavlink WL-WN570HA1
  2. Verify firmware version
    Navigate to the device web interface status or firmware upgrade page and locate the firmware version string, or check via SSH/Telnet if available using 'cat /etc/version' or similar command
    Affected if The firmware version is exactly R70HA1 V1410_221110
  3. Check if adm.cgi is accessible
    Attempt to access http://<device_ip>/cgi-bin/adm.cgi in a web browser or via curl command. A valid response (even an error or login prompt) indicates the CGI is reachable
    Affected if The /cgi-bin/adm.cgi endpoint responds to HTTP requests
  4. Determine if remote management is enabled
    In the device web interface, check the Administration or System settings for remote management access (WAN access) configuration. Look for settings like 'Remote Management', 'Web Management', or 'Admin Access' that may allow access from WAN IP addresses
    Affected if Remote (WAN) access to the web interface is enabled

A user is affected if they are running firmware version R70HA1 V1410_221110 on a Wavlink WL-WN570HA1 device with the web interface accessible, especially if remote management is enabled

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 removed the firmware and discontinued support for this product with no patch available, the recommended remediation is to decommission and replace the affected device with a currently supported model. If the device must remain in service, implement strict network segmentation and firewall rules to block external access to the administrative CGI interface.

Recommended fix Moderate confidence
  1. The Wavlink WL-WN570HA1 firmware version R70HA1_V1410_221110 is end-of-life and no longer supported by the vendor.
  2. The vendor has explicitly removed this firmware version from their website and states the affected product is no longer maintained.
  3. No official patch or fixed firmware version is available for this vulnerability.
  4. Replace the affected Wavlink WL-WN570HA1 device with a currently supported model from Wavlink or an alternative vendor.
  5. If device replacement is not immediately possible, network-segment the device behind a firewall with strict access controls to limit remote attack surface.
  6. Monitor the vendor website for any future security updates, though none are currently announced for this end-of-life product.
Caveat This is an end-of-life product with no available upgrade path; the device must be replaced

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

Fix this in Wl Wn570ha1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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