# CVE-2020-13117: Command injection in n/a

> Unauthenticated remote attackers can execute arbitrary commands on Wavlink routers via the login key parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2021
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-377v-3m99-jhrj

## What is CVE-2020-13117?

CVE-2020-13117 is a critical command injection vulnerability in n/a, published on 9 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wavlink WN575A4, WN579X3, and WN530G3A devices through 2020-05-15 allow unauthenticated remote users to inject commands via the key parameter in a login request.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 2 products.


Products: Wavlink Wn575a4 Firmware, Wavlink Wn579x3 Firmware.

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

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

## Is CVE-2020-13117 being exploited?

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

Public exploit code:

- Wavlink Multiple AP - Remote Command Injection (nuclei): http/cves/2020/CVE-2020-13117.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13117 is a critical command injection vulnerability in n/a, published on 9 Feb 2021. 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-13117 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-13117/ (Markdown: https://insights.sbomify.com/CVE-2020-13117/index.md)
```

## Sources

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

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