CVE-2020-9054

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2020-29883 (ENISA EUVD) · GHSA-w6h5-rjp3-hxvc (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

The vendor states that a fix is released ("ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, NAS542, ATP100, ATP200, ATP500, ATP800, USG20-VPN, USG20W-VPN, USG40, USG40W, USG60, USG60W, USG110, USG210, USG310, USG1100, USG1900, USG2200, VPN50…"), but the CVE record does not name the fixed version — check the vendor's advisory for the fixed release and apply it.

Multiple ZyXEL network-attached storage (NAS) devices running firmware version 5.21 contain a pre-authentication command injection vulnerability, which may allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable device. ZyXEL NAS devices achieve authentication by using the weblogin.cgi CGI executable. This program fails to properly sanitize the username parameter that is passed to it. If the username parameter contains certain characters, it can allow command injection with the privileges of the web server that runs on the ZyXEL device. Although the web server does not run as the root user, ZyXEL devices include a setuid utility that can be leveraged to run any command with root privileges. As such, it should be assumed that exploitation of this vulnerability can lead to remote code execution with root privileges. By sending a specially-crafted HTTP POST or GET request to a vulnerable ZyXEL device, a remote, unauthenticated attacker may be able to execute arbitrary code on the device. This may happen by directly connecting to a device if it is directly exposed to an attacker. However, there are ways to trigger such crafted requests even if an attacker does not have direct connectivity to a vulnerable devices. For example, simply visiting a website can result in the compromise of any ZyXEL device that is reachable from the client system. Affected products include: NAS326 before firmware V5.21(AAZF.7)C0 NAS520 before firmware V5.21(AASZ.3)C0 NAS540 before firmware V5.21(AATB.4)C0 NAS542 before firmware V5.21(ABAG.4)C0 ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, and NAS542 devices. Affected models that are end-of-support: NSA210, NSA220, NSA220+, NSA221, NSA310, NSA310S, NSA320, NSA320S, NSA325 and NSA325v2

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
84
EG Risk 84/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The vendor states that a fix is released ("ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, NAS542, ATP100, ATP200, ATP500, ATP800, USG20-VPN, USG20W-VPN, USG40, USG40W, USG60, USG60W, USG110, USG210, USG310, USG1100, USG1900, USG2200, VPN50…"), but the CVE record does not name the fixed version. Check the vendor's advisory for the fixed release and apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
>99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

The vendor states that a fix is released ("ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, NAS542, ATP100, ATP200, ATP500, ATP800, USG20-VPN, USG20W-VPN, USG40, USG40W, USG60, USG60W, USG110, USG210, USG310, USG1100, USG1900, USG2200, VPN50…"), but the CVE record does not name the fixed version. Check the vendor's advisory for the fixed release and apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2020-9054

Published

March 4, 2020

Last Modified

October 8, 2026

Advisory Details (5)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Vendor states a fix is released — the CVE record does not name the version. Sources: cert.
Web pageMentions a patch (unverified)🟡 PoC Available

Zyxel Fixes 0day in Network Storage Devices – Krebs on Security

https://krebsonsecurity.com/2020/02/zyxel-fixes-0day-in-network-storage-devices/
CERT

VU#498544 - ZyXEL pre-authentication command injection in weblogin.cgi

https://kb.cert.org/vuls/id/498544/
Web page

CWE - CWE-78: Improper Neutralization of Special Elements used in an OS Command (5.0)

https://cwe.mitre.org/data/definitions/78.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 101× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 959 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 859 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 12:14 UTCEG score recompute
  2. 2026-11-02 12:14 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  3. 2026-11-01 10:40 UTCEG score recompute
  4. 2026-11-01 10:40 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  5. 2026-10-31 09:08 UTCEG score recompute
  6. 2026-10-31 09:08 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  7. 2026-10-30 07:36 UTCEG score recompute
  8. 2026-10-30 07:36 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  9. 2026-10-29 06:04 UTCEG score recompute
  10. 2026-10-29 06:04 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  11. 2026-10-28 04:31 UTCEG score recompute
  12. 2026-10-28 04:31 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  13. 2026-10-27 02:59 UTCEG score recompute
  14. 2026-10-27 02:59 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  15. 2026-10-26 01:26 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  16. 2026-10-25 18:38 UTCEG score recompute
  17. 2026-10-25 16:28 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  18. 2026-10-24 23:54 UTCEG score recompute
  19. 2026-10-24 23:54 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  20. 2026-10-23 22:23 UTCEG score recompute
  21. 2026-10-23 22:22 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  22. 2026-10-22 20:50 UTCEG score recompute
  23. 2026-10-22 20:50 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  24. 2026-10-21 19:16 UTCEG score recompute
  25. 2026-10-21 19:16 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-20 17:44 UTCEG score recompute
  2. 2026-10-20 17:44 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  3. 2026-10-19 16:10 UTCEG score recompute
  4. 2026-10-19 16:10 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  5. 2026-10-18 14:36 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  6. 2026-10-18 09:16 UTCEG score recompute
  7. 2026-10-17 13:04 UTCEG score recompute
  8. 2026-10-17 13:03 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  9. 2026-10-16 11:30 UTCEG score recompute
  10. 2026-10-16 11:30 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  11. 2026-10-15 09:57 UTCEG score recompute
  12. 2026-10-15 09:57 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  13. 2026-10-14 16:28 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  14. 2026-10-14 08:23 UTCEG score recompute
  15. 2026-10-14 08:23 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  16. 2026-10-13 06:49 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  17. 2026-10-12 19:29 UTCEG score recompute
  18. 2026-10-12 05:15 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  19. 2026-10-12 01:26 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  20. 2026-10-11 21:37 UTCEG score recompute
  21. 2026-10-11 21:37 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  22. 2026-10-11 17:49 UTCEG score recompute
  23. 2026-10-11 17:48 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  24. 2026-10-11 13:59 UTCEG score recompute
  25. 2026-10-11 13:58 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  26. 2026-10-11 10:10 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  27. 2026-10-11 06:22 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  28. 2026-10-11 02:34 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  29. 2026-10-10 22:47 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  30. 2026-10-10 18:58 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  31. 2026-10-10 15:11 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  32. 2026-10-10 11:22 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  33. 2026-10-10 07:34 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  34. 2026-10-10 03:46 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  35. 2026-10-09 23:58 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  36. 2026-10-09 20:09 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  37. 2026-10-09 16:22 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  38. 2026-10-09 12:34 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  39. 2026-10-09 08:43 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  40. 2026-10-09 04:55 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  41. 2026-10-09 01:05 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  42. 2026-10-08 21:17 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  43. 2026-10-08 17:29 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  44. 2026-10-08 13:41 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  45. 2026-10-08 09:51 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  46. 2026-10-08 06:02 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  47. 2026-10-08 02:15 UTCEG score recompute
  48. 2026-10-08 02:14 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  49. 2026-10-07 23:44 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  50. 2026-10-07 22:26 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  51. 2026-10-07 18:38 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  52. 2026-10-07 17:47 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  53. 2026-10-07 17:09 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  54. 2026-10-07 13:19 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  55. 2026-10-07 09:31 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  56. 2026-10-07 05:42 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  57. 2026-10-07 01:54 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  58. 2026-10-06 22:03 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  59. 2026-10-06 18:15 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  60. 2026-10-06 14:27 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  61. 2026-10-06 10:39 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  62. 2026-10-06 06:50 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  63. 2026-10-06 02:59 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  64. 2026-10-05 23:11 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  65. 2026-10-05 19:21 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  66. 2026-10-05 15:33 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  67. 2026-10-05 11:45 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  68. 2026-10-05 07:58 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  69. 2026-10-05 04:10 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  70. 2026-10-05 00:21 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  71. 2026-10-04 20:31 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  72. 2026-10-04 16:43 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  73. 2026-10-04 12:55 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  74. 2026-10-04 09:06 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8
  75. 2026-10-04 05:17 UTCGHSA enrichmentGHSA-w6h5-rjp3-hxvc · GitHub severity HIGH · GitHub CVSS 9.8

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCdarrenmartyn/CVE-2020-9054
    Published Sep 9, 2021

    CVE-2020-9054 PoC for Zyxel

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-9054.yaml
    Published May 2, 2021

    Zyxel NAS Firmware 5.21- Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2020-9054?
CVE-2020-9054 is a critical-severity vulnerability; its CVE record was published on March 4, 2020. Multiple ZyXEL network-attached storage (NAS) devices running firmware version 5.21 contain a pre-authentication command injection vulnerability, which may allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable device. ZyXEL NAS devices achieve authentication by using…
When was CVE-2020-9054 made public?
CVE-2020-9054 was made public on February 20, 2020: that is the date its CVE record's CNA, CERT/CC, gives for when the vulnerability was made public. The CVE record itself was published on March 4, 2020. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2020-9054 actively exploited?
Yes. CISA added CVE-2020-9054 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Zyxel Multiple Network-Attached Storage (NAS) Devices. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. The vendor states that a fix is released ("ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, NAS542, ATP100, ATP200, ATP500, ATP800, USG20-VPN, USG20W-VPN, USG40, USG40W, USG60, USG60W, USG110, USG210, USG310, USG1100, USG1900, USG2200, VPN50…"), but the CVE record does not name the fixed version. Check the vendor's advisory for the fixed release and apply it.
What is the CVSS score of CVE-2020-9054?
CVE-2020-9054 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2020-9054?
CVE-2020-9054 affects Zyxel Multiple Network-Attached Storage (NAS) Devices.
How do I remediate CVE-2020-9054?
The CVE record for CVE-2020-9054 states that the vendor has released a fix: "ZyXEL has made firmware updates available for NAS326, NAS520, NAS540, NAS542, ATP100, ATP200, ATP500, ATP800, USG20-VPN, USG20W-VPN, USG40, USG40W, USG60, USG60W, USG110, USG210, USG310, USG1100, USG1900, USG2200, VPN50…" The record does not name the fixed version: check the vendor's advisory for the fixed release and update to it.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-9054

Explore →

Is Your Infrastructure Affected by CVE-2020-9054?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.