dbcve.org
Wl Wn575a3 FirmwareOperating system · Wavlink

CVE-2020-10971

HIGH · 8.8 CVSS v3.1 Published 2020-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An issue was discovered on Wavlink Jetstream devices where a crafted POST request can be sent to adm.cgi that will result in the execution of the supplied command if there is an active session at the same time. The POST request itself is not validated to ensure it came from the active session. Affected devices are: Wavlink WN530HG4, Wavlink WN575A3, Wavlink WN579G3,Wavlink WN531G3, Wavlink WN533A8, Wavlink WN531A6, Wavlink WN551K1, Wavlink WN535G3, Wavlink WN530H4, Wavlink WN57X93, WN572HG3, Wavlink WN578A2, Wavlink WN579G3, Wavlink WN579X3, and Jetstream AC3000/ERAC3000

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

Wavlink Jetstream devices contain a vulnerability in adm.cgi where POST requests are not validated to ensure they originated from an active session. An attacker with an active session can send crafted requests that result in arbitrary command execution on the affected devices. This affects multiple Wavlink models including WN530HG4, WN575A3, WN579G3, WN531G3, and others, as well as Jetstream AC3000/ERAC3000.

MitigationApply vendor firmware updates when available; if no patch exists, implement network segmentation to isolate affected devices and consider device replacement.

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 Wn575a3 FirmwareOperating system
Affected:= rpt75a3.v4300.180801
Wl Wn530hg4 FirmwareOperating system
Affected:= m30hg4.v5030.191116
Wl Wn579g3 FirmwareOperating system
Affected:= m79x3.v5030.180719

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 device model
    Access the device web interface or check the device label/marketing to confirm the exact model number (e.g., WN530HG4, WN575A3, WN579G3, WN531G3, AC3000, ERAC3000).
    Affected if The device is any Wavlink or Jetstream model listed in the affected products.
  2. Check the firmware version
    Log into the device web interface and navigate to the Status or System Info page to view the firmware version. Compare against: rpt75a3.v4300.180801 (WN575A3), m30hg4.v5030.191116 (WN530HG4), m79x3.v5030.180719 (WN579G3).
    Affected if The installed firmware version exactly matches one of the listed vulnerable versions.
  3. Verify adm.cgi endpoint is accessible
    Attempt to access http://<device_ip>/adm.cgi via a web browser or curl command. If the page loads or responds, the endpoint is exposed.
    Affected if The adm.cgi endpoint responds to HTTP requests, indicating the web interface is active.
  4. Confirm the device web interface is reachable on the network
    Ping the device IP address and attempt a TCP connection to port 80 or 443 to verify network accessibility of the management interface.
    Affected if The device web management interface is reachable from the network where the check is performed.

You are affected if you have one of the listed Wavlink/Jetstream models running any of the specified firmware versions and the adm.cgi web interface is network-accessible.

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

Apply vendor firmware updates when available; if no patch exists, implement network segmentation to isolate affected devices and consider device replacement.

Fix this in Wl Wn575a3 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-2020-10971 — 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-2020-10971 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