CVE-2024-21773 json
Multiple TP-LINK products allow a network-adjacent unauthenticated attacker with access to the product from the LAN port or Wi-Fi to execut…
published 2024-01-10 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-19387
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
Multiple TP-LINK products allow a network-adjacent unauthenticated attacker with access to the product from the LAN port or Wi-Fi to execute arbitrary OS commands on the product that has pre-specified target devices and blocked URLs in parental control settings.
Patch / fix
- tp-link archer_ax3000_firmware 1.1.2
- tp-link archer_ax5400_firmware 1.1.2
- tp-link deco_x50_firmware 1.4.1
- tp-link deco_xe200_firmware 1.2.5
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- TP-Link Archer AX3000
- TP-Link Archer AX5400
- TP-Link Deco X50
- TP-Link Deco XE200
- TP-Link Archer Air R5
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
tp-link.com
/jp/support/download/archer-ax3000/#Firmware
product
-
tp-link.com
/jp/support/download/archer-ax5400/#Firmware
product
-
tp-link.com
/jp/support/download/deco-x50/v1/#Firmware
product
-
tp-link.com
/jp/support/download/deco-xe200/#Firmware
product
- tp-link.com /jp/support/download/archer-air-r5/v1/#Firmware
-
jvn.jp
/en/vu/JVNVU91401812/
third-party-advisory
Sources
- CVE List CVE-2024-21773
- NVD CVE-2024-21773
Fencer Vulns 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.