CVE-2020-9375 in the critical feed json
TP-Link Archer C50 V3 devices before Build 200318 Rel.
published 6y ago modified 4mo ago also EUVD-2020-30196
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.7%
- EPSS 26.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
TP-Link Archer C50 V3 devices before Build 200318 Rel. 62209 allows remote attackers to cause a denial of service via a crafted HTTP Header containing an unexpected Referer field.
Is CVE-2020-9375 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-48255)
Exploit prediction
26.68% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-48255 TP-Link Archer C50 3 - Denial of Service (PoC) dos, 2020-03-26
- thewhiteh4t.github.io https://thewhiteh4t.github.io/2020/02/27/CVE-2020-9375-TP-Link-Archer-C50-v3-Denial-of-Service.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/156928/TP-Link-Archer-C50-V3-Denial-of-Service.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-772 Missing Release of Resource after Effective Lifetime
References
-
thewhiteh4t.github.io
/2020/02/27/CVE-2020-9375-TP-Link-Archer-C50-v3-Denial-of-Service.html
exploit, third-party-advisory
-
packetstormsecurity.com
/files/156928/TP-Link-Archer-C50-V3-Denial-of-Service.html
exploit, third-party-advisory
-
tp-link.com
/in/support/download/archer-c50/v3/#Firmware
release-notes, vendor-advisory
- thewhiteh4t.github.io /blog/cve-2020-9375-tplink/
Sources
- CVE List CVE-2020-9375
- NVD CVE-2020-9375
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.