# CVE-2020-10973: Information disclosure in n/a

> Unauthenticated attackers can retrieve the administrator password from Wavlink routers via a crafted POST request, leading to full device compromise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pr83-4gh9-4jr6

## What is CVE-2020-10973?

CVE-2020-10973 is a high-severity vulnerability in n/a, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2020-10973?

It affects 4 products.


Products: Wavlink Wn530hg4 Firmware, Wavlink Wn531g3 Firmware, Wavlink Wn533a8 Firmware, Wavlink Wn551k1 Firmware.

## How do I fix CVE-2020-10973?

No fix has been published for CVE-2020-10973 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-10973 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-10973 exists.

Public exploit code:

- WAVLINK - Access Control (nuclei): http/cves/2020/CVE-2020-10973.yaml

## Other vulnerabilities in n/a

- [CVE-2020-10972](https://insights.sbomify.com/CVE-2020-10972/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10973 and fix it if it is affected.

What it is: CVE-2020-10973 is a high-severity vulnerability in n/a, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-10973 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-10973/ (Markdown: https://insights.sbomify.com/CVE-2020-10973/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10973
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10973
- OSV: https://osv.dev/vulnerability/CVE-2020-10973

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10973/
Summaries are generated and may contain mistakes; the official description above is the record.