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

> Unauthenticated attackers can view the administrator password in cleartext on a specific router page, 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-w57h-38rg-v7ww

## What is CVE-2020-10972?

CVE-2020-10972 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 where a page is exposed that has the current administrator password in cleartext in the source code of the page. No authentication is required in order to reach the page (a certain live_?.shtml page with the variable syspasswd). Affected Devices: Wavlink WN530HG4, Wavlink WN531G3, and Wavlink WN572HG3

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 3 products.


Products: Wavlink Wn530hg4 Firmware, Wavlink Wn531g3 Firmware, Wavlink Wn572hg3 Firmware.

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

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

## Is CVE-2020-10972 being exploited?

There is no known exploitation of CVE-2020-10972 in the wild and no public exploit code.

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10972 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: There is no known exploitation of CVE-2020-10972 in the wild and no public exploit code.

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-10972/ (Markdown: https://insights.sbomify.com/CVE-2020-10972/index.md)
```

## Sources

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

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