Tl-wdr4300 Firmware
7 CVEs tracked. 2 of them are in CISA KEV.
This hub aggregates every CVE we track for Tl-wdr4300 Firmware, a product in the networking infrastructure space. Use it to gauge the current risk picture and drill into individual advisories.
Tl-wdr4300 Firmware CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 7 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical1
- High3
- Medium3
Latest CVEs
The 7 most recently published vulnerabilities affecting Tl-wdr4300 Firmware.
- CVE-2023-50224TP-Link TL-WR841N dropbearpwd Improper Authentication Information Disclosure Vulnerability6.5
- CVE-2013-4654Symlink Traversal vulnerability in TP-LINK TL-WDR4300 and TL-1043ND..9.8
- CVE-2013-4848TP-Link TL-WDR4300 version 3.13.31 has multiple CSRF vulnerabilities.8.8
- CVE-2019-6487TP-Link WDR Series devices through firmware v3 (such as TL-WDR5620 V3.0) are affected by command injection (after login) leading to remote code execution, because shell metacharacters can be includ...8.8
- CVE-2015-3035Directory traversal vulnerability in TP-LINK Archer C5 (1.2) with firmware before 150317, C7 (2.0) with firmware before 150304, and C8 (1.0) with firmware before 150316, Archer C9 (1.0), TL-WDR3500...7.5
- CVE-2014-4727Cross-site scripting (XSS) vulnerability in the DHCP clients page in the TP-LINK N750 Wireless Dual Band Gigabit Router (TL-WDR4300) with firmware before 140916 allows remote attackers to inject ar...4.3
- CVE-2014-4728The web server in the TP-LINK N750 Wireless Dual Band Gigabit Router (TL-WDR4300) with firmware before 140916 allows remote attackers to cause a denial of service (crash) via a long header in a GET...5.0
Product grouping is registry-driven, with AI assist and human review. How it works