TL-WR841N
TP-Link- Product type
- Other
- Catalog vulnerabilities
- 11
Severity across 6 analyzed records
Verify to analyze this security profile
en
As of 10/06/2026, within CyStack's analyzed data, TL-WR841N has 0 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of TL-WR841N and determine which vulnerabilities affect that version.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2023-50224TP-Link TL-WR841N dropbearpwd Improper Authentication Information Disclosure Vulnerability | Exploitation statusKEV | FixNot confirmed | Published05/03/2024 | SeverityMedium |
CVE-2023-39471TP-Link TL-WR841N ated_tp Command Injection Remote Code Execution Vulnerability | Exploitation statusNot known exploited | FixNot confirmed | Published05/03/2024 | SeverityHigh |
CVE-2023-36489 | Exploitation statusNot known exploited | FixNot confirmed | Published09/06/2023 | SeverityUnknown |
CVE-2023-39745 | Exploitation statusNot known exploited | FixNot confirmed | Published08/21/2023 | SeverityUnknown |
CVE-2023-36354 | Exploitation statusNot known exploited | FixNot confirmed | Published06/22/2023 | SeverityUnknown |
CVE-2022-42433 | Exploitation statusNot known exploited | FixNot confirmed | Published03/29/2023 | SeverityMedium |
CVE-2022-0162Vulnerability in TP-LinK TL-WR841N wireless router | Exploitation statusNot confirmed | FixYes | Published02/09/2022 | SeverityHigh |
CVE-2019-17147 | Exploitation statusNot confirmed | FixNot confirmed | Published01/07/2020 | SeverityHigh |
CVE-2012-6316 | Exploitation statusNot confirmed | FixNot confirmed | Published09/30/2014 | SeverityUnknown |
CVE-2012-6276 | Exploitation statusNot confirmed | FixNot confirmed | Published01/26/2013 | SeverityUnknown |
CVE-2012-5687 | Exploitation statusNot confirmed | FixNot confirmed | Published11/01/2012 | SeverityUnknown |