NetSight

Security Dashboard

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

Reset
611 matching advisories · page 7 of 21Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.2 CVE-2025-6151 A vulnerability has been found in TP-Link TL-WR940N V4 and TL-WR841N V11. tp-link · tl-wr940n_firmware 2025-06-17 high8.8 CVE-2025-5875 A vulnerability classified as critical has been found in TP-LINK Technologies TL-IPC544EP-W4 1.0.9 Build 240428 Rel 69493n. tp-link · tl-ipc544ep-w4_firmware 2025-06-09 critical9.2 CVE-2025-40634 Stack-based buffer overflow vulnerability in the 'conn-indicator' binary running as root on the TP-Link Archer AX50 router, in firmware versions prior to 1.0.1… firmware 2025-05-20 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 critical9.8 CVE-2024-57040 TP-Link TL-WR845N devices with firmware TL-WR845N(UN)_V4_200909 and TL-WR845N(UN)_V4_190219 was discovered to contain a hardcoded password for the root account… tp-link · tl-wr845n_firmware 2025-02-26 high7.5 CVE-2025-25901 A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11, triggered by the dnsserver1 and dnsserver2 parameters at /userRpm/WanSlaacCfgRpm.htm. tp-link · tl-wr841nd_firmware 2025-02-13 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 low3.5 CVE-2025-25899 A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the 'gw' parameter at /userRpm/WanDynamicIpV6CfgRpm.htm. tp-link · tl-wr841nd_v11_firmware 2025-02-13 high7.5 CVE-2025-25898 A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the pskSecret parameter at /userRpm/WlanSecurityRpm.htm. tp-link · tl-wr841nd_firmware 2025-02-13 high7.5 CVE-2025-25897 A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the 'ip' parameter at /userRpm/WanStaticIpV6CfgRpm.htm. tp-link · tl-wr841nd_firmware 2025-02-13 high8.0 CVE-2024-57357 An issue in TPLINK TL-WPA 8630 TL-WPA8630(US)_V2_2.0.4 Build 20230427 allows a remote attacker to execute arbitrary code via function sub_4256CC, which allows … tp-link · tl-wpa8630_firmware 2025-02-07 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 low3.7 CVE-2025-0730 A vulnerability classified as problematic has been found in TP-Link TL-SG108E 1.0.0 Build 20201208 Rel. tp-link · tl-sg108e_firmware 2025-01-27 medium4.3 CVE-2025-0729 A vulnerability was found in TP-Link TL-SG108E 1.0.0 Build 20201208 Rel. 2025-01-27 high8.0 CVE-2024-54887 TP-Link TL-WR940N V3 and V4 with firmware 3.16.9 and earlier contain a buffer overflow via the dnsserver1 and dnsserver2 parameters at /userRpm/Wan6to4TunnelCf… tp-link · tl-wr940n_firmware 2025-01-09 high8.0 CVE-2024-46341 TP-Link TL-WR845N(UN)_V4_190219 was discovered to transmit credentials in base64 encoded form, which can be easily decoded by an attacker executing a man-in-th… tp-link · tl-wr845n_firmware 2024-12-10 critical9.8 CVE-2024-46340 TL-WR845N(UN)_V4_201214, TP-Link TL-WR845N(UN)_V4_200909, and TL-WR845N(UN)_V4_190219 was discovered to transmit user credentials in plaintext after executing … tp-link · tl-wr845n_firmware 2024-12-10 high8.0 CVE-2024-50699 TP-Link TL-WR845N(UN)_V4_201214, TL-WR845N(UN)_V4_200909 and TL-WR845N(UN)_V4_190219 were discovered to contain weak default credentials for the Administrator … tp-link · tl-wr845n_firmware 2024-12-10 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 high8.5 CVE-2024-54126 This vulnerability exists in the TP-Link Archer C50 due to improper signature verification mechanism in the firmware upgrade process at its web interface. 2024-12-05 high8.0 CVE-2024-53375 An Authenticated Remote Code Execution (RCE) vulnerability affects the TP-Link Archer router series. 2024-12-02 high7.5 CVE-2024-53623 Incorrect access control in the component l_0_0.xml of TP-Link ARCHER-C7 v5 allows attackers to access sensitive information. 2024-11-29 high8.0 CVE-2024-48288 TP-Link TL-IPC42C V4.0_20211227_1.0.16 is vulnerable to command injection due to the lack of malicious code verification on both the frontend and backend. tp-link · tl-ipc42c_firmware 2024-11-21 high7.5 CVE-2024-11237 A vulnerability, which was classified as critical, has been found in TP-Link VN020 F3v(T) TT_V6.2.1021. tp-link · vn020-f3v\(t\)_firmware 2024-11-15 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 high7.5 CVE-2024-22733 TP Link MR200 V4 Firmware version 210201 was discovered to contain a null-pointer-dereference in the web administration panel on /cgi/login via the sign, Actio… tp-link · mr200_firmware 2024-11-01

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.