NetSight

Security Dashboard

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

Reset
566 matching advisories · page 2 of 19Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2025-51658 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_InquiryView.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51657 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the lgid parameter at SEMCMS_Link.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51656 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_Link.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51655 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Quanxian.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51654 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Infocategories.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51653 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_ct.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51652 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Categories.php. sem-cms · semcms 2025-07-14 medium5.5 CVE-2025-38332 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering … linux · linux_kernel, debian · debian_linux 2025-07-10 medium5.5 CVE-2025-38258 In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: free old damon_sysfs_scheme_filter->memcg_path on write memcg_path_… linux · linux_kernel 2025-07-09 medium4.8 CVE-2025-32366 In ConnMan through 1.44, parse_rr in dnsproxy.c has a memcpy length that depends on an RR RDLENGTH value, i.e., *rdlen=ntohs(rr->rdlen) and memcpy(response+off… ConnMan 2025-04-05 medium5.5 CVE-2023-52939 In the Linux kernel, the following vulnerability has been resolved: mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath() As commit 18365225… linux · linux_kernel 2025-03-27 medium5.5 CVE-2025-21834 In the Linux kernel, the following vulnerability has been resolved: seccomp: passthrough uretprobe systemcall without filtering When attaching uretprobes to pr… linux · linux_kernel 2025-03-06 medium5.5 CVE-2024-57977 In the Linux kernel, the following vulnerability has been resolved: memcg: fix soft lockup in the OOM process A soft lockup issue was found in the product with… linux · linux_kernel, Linux · Linux 2025-02-27 medium6.8 CVE-2024-57961 Out-of-bounds write vulnerability in the emcom module Impact: Successful exploitation of this vulnerability may cause features to perform abnormally. huawei · emui, huawei · harmonyos 2025-02-06 medium6.3 CVE-2024-13193 A vulnerability has been found in SEMCMS up to 4.8 and classified as critical. sem-cms · semcms 2025-01-08 medium6.5 CVE-2025-22365 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Eric McNiece EMC2 Alert Boxes allows Stored XSS.This issu… EMC2 Alert Boxes: from n/a 2025-01-07 medium5.3 CVE-2024-56738 GNU GRUB (aka GRUB2) through 2.12 does not use a constant-time algorithm for grub_crypto_memcmp and thus allows side-channel attacks. gnu · grub2 2024-12-29 medium5.5 CVE-2024-56539 In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan() Replace o… linux · linux_kernel 2024-12-27 medium5.5 CVE-2024-12662 A vulnerability classified as problematic has been found in IObit Advanced SystemCare Utimate up to 17.0.0. iobit · advanced_systemcare_ultimate 2024-12-16 medium5.5 CVE-2024-12661 A vulnerability was found in IObit Advanced SystemCare Utimate up to 17.0.0. iobit · advanced_systemcare_ultimate 2024-12-16 medium5.5 CVE-2024-12660 A vulnerability was found in IObit Advanced SystemCare Utimate up to 17.0.0. iobit · advanced_systemcare_ultimate 2024-12-16 medium5.5 CVE-2024-12659 A vulnerability was found in IObit Advanced SystemCare Utimate up to 17.0.0. iobit · advanced_systemcare_ultimate 2024-12-16 medium5.5 CVE-2024-12658 A vulnerability was found in IObit Advanced SystemCare Utimate up to 17.0.0 and classified as problematic. iobit · advanced_systemcare_ultimate 2024-12-16 medium5.5 CVE-2024-12657 A vulnerability has been found in IObit Advanced SystemCare Utimate up to 17.0.0 and classified as problematic. iobit · advanced_systemcare_ultimate 2024-12-16 medium6.7 CVE-2018-9404 In oemCallback of ril.cpp, there is a possible out of bounds write due to an integer overflow. google · android 2024-12-05 medium4.9 CVE-2024-52725 SemCms v4.8 was discovered to contain a SQL injection vulnerability. sem-cms · semcms 2024-11-20 medium5.3 CVE-2024-24450 Stack-based memcpy buffer overflow in the ngap_handle_pdu_session_resource_setup_response routine in OpenAirInterface CN5G AMF <= 2.0.0 allows a remote attacke… OpenAirInterface CN5G AMF 2024-11-15 medium5.5 CVE-2024-50008 In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() R… linux · linux_kernel 2024-10-21 medium6.8 CVE-2024-23961 Alpine Halo9 UPDM_wemCmdUpdFSpeDecomp Command Injection Remote Code Execution Vulnerability. alpsalpine · ilx-f509_firmware 2024-09-28 medium6.8 CVE-2024-23924 Alpine Halo9 UPDM_wemCmdCreatSHA256Hash Command Injection Remote Code Execution Vulnerability. alpsalpine · ilx-f509_firmware 2024-09-28

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.