NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
177 matching advisories · page 3 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2025-8065 A stack-based buffer overflow vulnerability was identified in the ONVIF SOAP XML Parser in Tapo C200 v3 and C520WS v2.6. tp-link · tapo_c200_firmware 2025-12-20 medium6.5 CVE-2025-14299 The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow. tp-link · tapo_c200_firmware 2025-12-20 medium6.8 CVE-2025-14739 Access of Uninitialized Pointer vulnerability in TP-Link WR940N and WR941ND allows local unauthenticated attackers the ability to execute DoS attack and potent… 2025-12-18 medium5.1 CVE-2025-6983 A Clickjacking vulnerability in TP-Link Archer C1200 web management page allows an attacker to trick users into performing unintended actions via rendered UI l… Archer C1200 2025-07-16 medium6.9 CVE-2025-6982 Use of Hard-coded Credentials in TP-Link Archer C50 V3( <= 180703)/V4( <= 250117 )/V5( <= 200407 ), and C20 V5 (<US_V5_260419 or <EU_V5_260317) allows attacker… 2025-07-16 medium5.4 CVE-2025-25427 A stored cross-site scripting (XSS) vulnerability in the upnp.htm page of the web Interface in TP-Link WR841N v14/v14.6/v14.8 <= Build 241230 Rel. tp-link · wr841n_firmware 2025-04-18 medium4.4 CVE-2025-3442 This vulnerability exists in TP-Link Tapo H200 V1 IoT Smart Hub due to storage of Wi-Fi credentials in plain text within the device firmware. 2025-04-09 medium4.9 CVE-2025-25900 A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the username and password parameters at /userRpm/PPPoEv6CfgRpm.htm. tp-link · tl-wr841nd_v11_firmware 2025-02-13 medium4.8 CVE-2024-57514 The TP-Link Archer A20 v3 router is vulnerable to Cross-site Scripting (XSS) due to improper handling of directory listing paths in the web interface. 2025-01-28 medium4.3 CVE-2025-0729 A vulnerability was found in TP-Link TL-SG108E 1.0.0 Build 20201208 Rel. 2025-01-27 medium6.3 CVE-2024-12344 A vulnerability, which was classified as critical, was found in TP-Link VN020 F3v(T) TT_V6.2.1021. tp-link · vn020_f3v_firmware 2024-12-08 medium6.5 CVE-2024-12343 A vulnerability classified as critical has been found in TP-Link VN020 F3v(T) TT_V6.2.1021. tp-link · vn020_f3v_firmware 2024-12-08 medium6.5 CVE-2024-12342 A vulnerability was found in TP-Link VN020 F3v(T) TT_V6.2.1021. 2024-12-08 medium4.3 CVE-2024-54127 This vulnerability exists in the TP-Link Archer C50 due to presence of terminal access on a serial interface without proper access control. 2024-12-05 medium4.6 CVE-2024-10523 This vulnerability exists in TP-Link IoT Smart Hub due to storage of Wi-Fi credentials in plain text within the device firmware. tp-link · tapo_h100_firmware 2024-11-04 medium6.5 CVE-2024-48714 In TP-Link TL-WDR7660 v1.0, the guestRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabili… tp-link · tl-wdr7660_firmware 2024-10-15 medium6.5 CVE-2024-48713 In TP-Link TL-WDR7660 1.0, the wacWhitelistJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabi… tp-link · tl-wdr7660_firmware 2024-10-15 medium6.5 CVE-2024-48712 In TP-Link TL-WDR7660 1.0, the rtRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabilities. tp-link · tl-wdr7660_firmware 2024-10-15 medium6.5 CVE-2024-48710 In TP-Link TL-WDR7660 1.0, the wlanTimerRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerab… tp-link · tl-wdr7660_firmware 2024-10-15 medium5.5 CVE-2024-46325 TP-Link WR740N V6 has a stack overflow vulnerability via the ssid parameter in /userRpm/popupSiteSurveyRpm.htm url. tp-link · wr740n_firmware 2024-10-07 medium4.3 CVE-2024-35495 An Information Disclosure vulnerability in the Telemetry component in TP-Link Kasa KP125M V1.0.0 and Tapo P125M 1.0.0 Build 220930 Rel.143947 allows attackers … 2024-09-30 medium6.3 CVE-2024-46548 TP-Link Tapo P125M and Kasa KP125M v1.0.3 was discovered to improperly validate certificates, allowing attackers to eavesdrop on communications and access sens… 2024-09-30 medium6.5 CVE-2024-9284 A vulnerability was found in TP-LINK TL-WR841ND up to 20240920. tp-link · tl-wr841nd_firmware 2024-09-27 medium5.4 CVE-2024-4224 An authenticated stored cross-site scripting (XSS) exists in the TP-Link TL-SG1016DE affecting version TL-SG1016DE(UN) V7.6_1.0.0 Build 20230616, which could a… 2024-07-15 medium6.8 CVE-2024-38471 Multiple TP-LINK products allow a network-adjacent attacker with an administrative privilege to execute arbitrary OS commands by restoring a crafted backup fil… 2024-07-04 medium6.3 CVE-2024-37662 TP-LINK TL-7DR5130 v1.0.23 is vulnerable to TCP DoS or hijacking attacks. tp-link · tl-7dr5130_firmware 2024-06-17 medium6.3 CVE-2024-37661 TP-LINK TL-7DR5130 v1.0.23 is vulnerable to forged ICMP redirect message attacks. tp-link · tl-7dr5130_firmware 2024-06-17 medium5.3 CVE-2023-30307 An issue discovered in TP-LINK TL-R473GP-AC, TP-LINK XDR6020, TP-LINK TL-R479GP-AC, TP-LINK TL-R4239G, TP-LINK TL-WAR1200L, and TP-LINK TL-R476G routers allows… 2024-05-28 medium4.2 CVE-2024-5244 TP-Link Omada ER605 Reliance on Security Through Obscurity Vulnerability. tp-link · omada_er605_firmware 2024-05-23 medium4.8 CVE-2024-31340 TP-Link Tether versions prior to 4.5.13 and TP-Link Tapo versions prior to 3.3.6 do not properly validate certificates, which may allow a remote unauthenticate… TP-Link Tether, TP-Link Tapo 2024-05-22

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.