dbcve.org
Wl Wn579g3 FirmwareOperating system · Wavlink

CVE-2020-12266

HIGH · 7.5 CVSS v3.1 Published 2020-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
An issue was discovered where there are multiple externally accessible pages that do not require any sort of authentication, and store system information for internal usage. The devices automatically query these pages to update dashboards and other statistics, but the pages can be accessed externally without any authentication. All the pages follow the naming convention live_(string).shtml. Among the information disclosed is: interface status logs, IP address of the device, MAC address of the device, model and current firmware version, location, all running processes, all interfaces and their statuses, all current DHCP leases and the associated hostnames, all other wireless networks in range of the router, memory statistics, and components of the configuration of the device such as enabled features. Affected devices: 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

Unauthenticated information disclosure vulnerability in Wavlink and Jetstream routers where multiple internal dashboard pages (live_*.shtml) are accessible externally without authentication. These pages expose sensitive system data including device IP/MAC addresses, firmware versions, running processes, DHCP leases with hostnames, wireless network details, memory statistics, and configuration settings.

MitigationImplement authentication on live_*.shtml pages or restrict access via firewall to internal networks only; contact vendor for firmware updates.

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 Wn579g3 FirmwareOperating system
Affected:= m79x3.v5030.180719
Wl Wn575a3 FirmwareOperating system
Affected:= rpt75a3.v4300.180801
Wl Wn530hg4 FirmwareOperating system
Affected:= m30hg4.v5030.191116
Wn531g3 FirmwareOperating system
Affected:all versions
Wn533a8 FirmwareOperating system
Affected:all versions
Wn531a6 FirmwareOperating system
Affected:all versions
Wn551k1 FirmwareOperating system
Affected:all versions
Wn535g3 FirmwareOperating system
Affected:all versions

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 and firmware version
    Access the router admin panel and check the system status or firmware information page, or use the command 'grep' or 'cat' on /etc/version or /proc/version if SSH/telnet is available
    Affected if The device is a Wavlink model Wn579g3, Wn575a3, Wn530hg4, Wn531g3, Wn533a8, Wn531a6, Wn551k1, or Wn535g3 with an affected firmware version (m79x3.v5030.180719, rpt75a3.v4300.180801, m30hg4.v5030.191116, or any version for Wn531g3/Wn533a8/Wn531a6/Wn551k1/Wn535g3)
  2. Determine if the router web interface is exposed to the internet
    Check router firewall settings or perform an external port scan (using a tool like nmap or an online port scanner) to see if HTTP (port 80) or HTTPS (port 443) is open to public IP addresses
    Affected if Ports 80 or 443 are accessible from external/public IP addresses (not just from internal LAN)
  3. Test unauthenticated access to live_*.shtml pages
    From an external network (or using the public IP), attempt to access URLs such as http://<router-public-ip>/live_topology.shtml, http://<router-public-ip>/live_statistics.shtml, or http://<router-public-ip>/live_dhcp.shtml without providing any login credentials
    Affected if Any live_*.shtml page loads and displays sensitive information (device IPs, MACs, firmware version, processes, DHCP leases, wireless settings, memory stats, or configuration data) without requiring authentication

A user is affected if they own a Wavlink router from the listed models with an affected firmware version AND the router web interface is exposed to the internet, allowing unauthenticated access to live_*.shtml pages that reveal sensitive system data.

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

Implement authentication on live_*.shtml pages or restrict access via firewall to internal networks only; contact vendor for firmware updates.

Fix this in Wl Wn579g3 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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