CVE-2020-10973
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 · uneditedAn issue was discovered in Wavlink WN530HG4, Wavlink WN531G3, Wavlink WN533A8, and Wavlink WN551K1 affecting /cgi-bin/ExportAllSettings.sh where a crafted POST request returns the current configuration of the device, including the administrator password. No authentication is required. The attacker must perform a decryption step, but all decryption information is readily available.
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 confidenceUnauthenticated information disclosure in Wavlink routers (WN530HG4, WN531G3, WN533A8, WN551K1). A crafted POST request to /cgi-bin/ExportAllSettings.sh returns the full device configuration including the encrypted administrator password. The decryption key is also exposed, allowing remote attackers to obtain plaintext admin credentials without authentication.
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= m30hg4.v5030.191116all versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelCheck the device label, admin web interface footer, or use SNMP/UPnP to determine if the device is a Wavlink WN530HG4, WN531G3, WN533A8, or WN551K1Affected if The device is one of these four models
-
Determine firmware versionLog into the router admin interface and check the firmware version in the status or system settings page, or query the device via SSH/Telnet if availableAffected if For WN530HG4: firmware is m30hg4.v5030.191116; for other models: any version
-
Test for vulnerable endpoint accessibilitySend a crafted POST request to http://<device_ip>/cgi-bin/ExportAllSettings.sh (no authentication required). Use: curl -X POST http://<router_ip>/cgi-bin/ExportAllSettings.shAffected if The endpoint returns a configuration file containing the encrypted admin password and decryption key
-
Check if remote management is enabledIn the router admin interface, look for 'Remote Management', 'Web Access from WAN', or 'External Access' settings. Verify if the web interface is bound to WAN interface or DMZ is configuredAffected if Remote management is enabled and the device is directly accessible from the internet, or the vulnerable CGI script is reachable from WAN
If the device is a Wavlink model WN530HG4, WN531G3, WN533A8, or WN551K1 and the /cgi-bin/ExportAllSettings.sh endpoint responds with configuration data (including encrypted password and key), the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware patches if available; otherwise, isolate the affected devices behind a firewall, disable remote management interfaces exposed to the internet, and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10973 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10973 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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