NetSight

Security Dashboard

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

Reset
428 matching advisories · page 5 of 15Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2025-6896 A vulnerability classified as critical has been found in D-Link DI-7300G+ 19.12.25A1. dlink · di-7300g\+_firmware 2025-06-30 medium6.3 CVE-2025-45729 D-Link DIR-823-Pro 1.02 has improper permission control, allowing unauthorized users to turn on and access Telnet services. dlink · dir-823_pro_firmware 2025-06-27 medium6.3 CVE-2025-5573 A vulnerability was found in D-Link DCS-932L 2.18.01. dlink · dcs-932l_firmware 2025-06-04 medium6.3 CVE-2025-5571 A vulnerability was found in D-Link DCS-932L 2.18.01. dlink · dcs-932l_firmware 2025-06-04 medium6.3 CVE-2025-5492 A vulnerability has been found in D-Link DI-500WF-WT up to 20250511 and classified as critical. dlink · di-500wf-wt_firmware 2025-06-03 medium6.5 CVE-2025-46176 Hardcoded credentials in the Telnet service in D-Link DIR-605L v2.13B01 and DIR-816L v2.06B01 allow attackers to remotely execute arbitrary commands via firmwa… dlink · dir-605l_firmware, dlink · dir-816l_firmware 2025-05-23 medium5.3 CVE-2025-4904 A vulnerability has been found in D-Link DI-7003GV2 24.04.18D1 R(68125) and classified as problematic. dlink · di-7003g_firmware 2025-05-19 medium5.3 CVE-2025-4903 A vulnerability, which was classified as critical, was found in D-Link DI-7003GV2 24.04.18D1 R(68125). dlink · di-7003g_firmware 2025-05-19 medium5.3 CVE-2025-4902 A vulnerability, which was classified as problematic, has been found in D-Link DI-7003GV2 24.04.18D1 R(68125). dlink · di-7003g_firmware 2025-05-19 medium4.3 CVE-2025-4901 A vulnerability classified as problematic was found in D-Link DI-7003GV2 24.04.18D1 R(68125). dlink · di-7003g_firmware 2025-05-19 medium5.3 CVE-2025-4756 A vulnerability was found in D-Link DI-7003GV2 24.04.18D1 R(68125). dlink · di-7003g_firmware 2025-05-16 medium5.3 CVE-2025-4753 A vulnerability was found in D-Link DI-7003GV2 24.04.18D1 R(68125) and classified as problematic. dlink · di-7003g_firmware 2025-05-16 medium5.3 CVE-2025-4752 A vulnerability has been found in D-Link DI-7003GV2 24.04.18D1 R(68125) and classified as problematic. dlink · di-7003g_firmware 2025-05-16 medium5.3 CVE-2025-4751 A vulnerability, which was classified as problematic, was found in D-Link DI-7003GV2 24.04.18D1 R(68125). dlink · di-7003g_firmware 2025-05-16 medium5.3 CVE-2025-4750 A vulnerability, which was classified as problematic, has been found in D-Link DI-7003GV2 24.04.18D1 R(68125). dlink · di-7003g_firmware 2025-05-16 medium6.6 CVE-2025-4544 A vulnerability was found in D-Link DI-8100 up to 16.07.26A1 and classified as critical. dlink · di-8100_firmware 2025-05-11 medium6.3 CVE-2025-4454 A vulnerability was found in D-Link DIR-619L 2.04B04. dlink · dir-619l_firmware 2025-05-09 medium6.3 CVE-2025-4453 A vulnerability was found in D-Link DIR-619L 2.04B04. dlink · dir-619l_firmware 2025-05-09 medium6.3 CVE-2025-4445 A vulnerability classified as critical has been found in D-Link DIR-605L 2.13B01. dlink · dir-605l_firmware 2025-05-09 medium6.3 CVE-2025-4443 A vulnerability was found in D-Link DIR-605L 2.13B01. dlink · dir-605l_firmware 2025-05-09 medium6.5 CVE-2025-44023 An issue in dlink DNS-320 v.1.00 and DNS-320LW v.1.01.0914.20212 allows an attacker to execute arbitrary via the account_mgr.cgi->cgi_chg_admin_pw components. 2025-05-08 medium6.3 CVE-2025-4341 A vulnerability classified as critical was found in D-Link DIR-880L up to 104WWb01. dlink · dir-880l_firmware 2025-05-06 medium6.3 CVE-2025-4340 A vulnerability classified as critical has been found in D-Link DIR-890L and DIR-806A1 up to 100CNb11/108B03. dlink · dir-806_firmware, dlink · dir-890l_firmware 2025-05-06 medium6.3 CVE-2025-44835 D-Link DIR-816 A2V1.1.0B05 was found to contain a command injection in iptablesWebsFilterRun, which allows remote attackers to execute arbitrary commands via s… dlink · dir-816_a2_firmware 2025-05-01 medium6.5 CVE-2025-29743 D-Link DIR-816 A2V1.1.0B05 was found to contain a command injection in /goform/delRouting. dlink · dir-816_firmware 2025-04-22 medium4.7 CVE-2025-2717 A vulnerability, which was classified as critical, has been found in D-Link DIR-823X 240126/240802. dlink · dir-823x_firmware 2025-03-25 medium4.3 CVE-2025-2553 A vulnerability was found in D-Link DIR-618 and DIR-605L 2.02/3.02. dlink · dir-618_firmware, dlink · dir-605l_firmware 2025-03-20 medium4.3 CVE-2025-2552 A vulnerability was found in D-Link DIR-618 and DIR-605L 2.02/3.02. dlink · dir-618_firmware, dlink · dir-605l_firmware 2025-03-20 medium4.3 CVE-2025-2551 A vulnerability was found in D-Link DIR-618 and DIR-605L 2.02/3.02. dlink · dir-618_firmware, dlink · dir-605l_firmware 2025-03-20 medium4.3 CVE-2025-2550 A vulnerability was found in D-Link DIR-618 and DIR-605L 2.02/3.02 and classified as problematic. dlink · dir-618_firmware, dlink · dir-605l_firmware 2025-03-20

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.