Cyber Resilience

CVE-2020-13117

RCE in Wavlink Wn575A4 Firmware ≤ 2020-05-15

Public PoCHigh EPSSRCECommand Injection
Published
09 February 2021
Modified
19 August 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.69 99.3th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2020-13117 is a critical-severity Command Injection (CWE-77) vulnerability in Wavlink Wn575A4 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 0.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-77

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
Unauthenticated remote command injection via the login key parameter directly enables exploitation of a public-facing web interface.
attack.mitre.org →
T1059 Command and Scripting Interpreter Executionconfidence: HIGH
The vulnerability permits injection of arbitrary OS commands, enabling execution via a command interpreter.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-50757Same vendor: Wavlink
CVE-2024-10428Same vendor: Wavlink
CVE-2024-39764Same vendor: Wavlink
CVE-2024-39763Same vendor: Wavlink
CVE-2024-39760Same vendor: Wavlink
CVE-2024-39759Same vendor: Wavlink
CVE-2023-3380Same product: Wavlink Wn579X3
CVE-2025-50756Same vendor: Wavlink
CVE-2024-10193Same vendor: Wavlink
CVE-2024-48705Same vendor: Wavlink

Affected Assets

wavlink
wn575a4 firmware
≤ 2020-05-15
wavlink
wn579x3 firmware
≤ 2020-05-15

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches command-injection vulnerabilities before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

A.8.31 Separation of development, test and production environments none match
none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References