NetSight

Security Dashboard

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

Reset
129 matching advisories · page 4 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-4mhf-vc39-9f4q Malicious code in added-yellow-tiglon (npm)Malware npm · added-yellow-tiglon 2026-08-31 critical GHSA-hvf6-cp3p-j28f Malicious code in yellorq (PyPI)Malware pip · yellorq 2026-07-21 critical GHSA-w3w4-49m4-5gr3 Malicious code in yellyproxies (PyPI)Malware pip · yellyproxies 2026-07-21 medium4.3 CVE-2026-8424 The Remove Yellow BGBOX plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. 2026-05-20 medium6.8 CVE-2026-45585 Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". microsoft · windows_11_24h2, microsoft · windows_11_25h2, microsoft · windows_11_26h1 +1 2026-05-20 critical GHSA-87w3-vjjr-47gf Malware in yellowdiscordlookupMalware npm · yellowdiscordlookup 2025-12-30 critical GHSA-h8cx-c2ww-pqxx Malware in yellow-pluginsMalware npm · yellow-plugins 2025-05-27 high7.1 CVE-2025-23995 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ta2g Tantyyellow allows Reflected XSS.This issue affects … Tantyyellow: from n/a 2025-03-31 critical GHSA-64hr-5cmh-c2gx Malware in mp3-file-zip-d-ownload-7517-goodbye-yellow-brick-road-h63vl-tpdnhxMalware npm · mp3-file-zip-d-ownload-7517-goodbye-yellow-brick-road-h63vl-tpdnhx 2024-10-16 high7.1 CVE-2024-47348 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in YellowPencil YellowPencil Visual CSS Style Editor yellow-… YellowPencil Visual CSS Style Editor: from n/a through 2024-10-06 high7.1 CVE-2024-43963 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in WaspThemes YellowPencil Visual CSS Style Editor al… waspthemes · yellowpencil 2024-08-29 medium5.4 CVE-2023-1110 The Yellow Yard Searchbar WordPress plugin before 2.8.12 does not validate and escape some of its shortcode attributes before outputting them back in a page/po… yellowyard · yellow_yard_searchbar 2023-08-16 critical9.8 CVE-2023-0750 Yellobrik PEC-1864 implements authentication checks via javascript in the frontend interface. lynx-technik · yellobrik_pec_1864_firmware 2023-04-06 medium6.1 CVE-2022-2094 The Yellow Yard Searchbar WordPress plugin before 2.8.2 does not escape some URL parameters before outputting them back to the user, leading to Reflected Cross… yellowyard · yellow_yard_searchbar 2023-02-08 critical GHSA-4rvw-2pjj-wcqq Malware in yellowbrainMalware npm · yellowbrain 2023-02-06 medium5.4 CVE-2020-19587 Cross Site Scripting (XSS) vulnerability in configMap parameters in Yellowfin Business Intelligence 7.3 allows remote attackers to run arbitrary code via MIAdm… idera · yellowfin_business_intelligence 2022-09-14 critical9.0 CVE-2020-19586 Incorrect Access Control issue in Yellowfin Business Intelligence 7.3 allows remote attackers to escalate privilege via MIAdminStyles.i4 Admin UI. yellowfinbi · business_intelligence 2022-09-14 critical GHSA-xv3m-jcfm-4m4v Malware in yello133Malware npm · yello133 2022-06-20 medium6.1 CVE-2021-24934 The Visual CSS Style Editor WordPress plugin before 7.5.4 does not sanitise and escape the wyp_page_type parameter before outputting it back in an admin page, … yellowpencil · visual_css_style_editor 2022-02-01 high7.5 CVE-2021-36389 In Yellowfin before 9.6.1 it is possible to enumerate and download uploaded images through an Insecure Direct Object Reference vulnerability exploitable by sen… yellowfinbi · yellowfin 2021-10-14 high7.5 CVE-2021-36388 In Yellowfin before 9.6.1 it is possible to enumerate and download users profile pictures through an Insecure Direct Object Reference vulnerability exploitable… yellowfinbi · yellowfin 2021-10-14 medium5.4 CVE-2021-36387 In Yellowfin before 9.6.1 there is a Stored Cross-Site Scripting vulnerability in the video embed functionality exploitable through a specially crafted HTTP PO… yellowfinbi · yellowfin 2021-10-14 high8.8 CVE-2019-14768 An Arbitrary File Upload issue in the file browser of DIMO YellowBox CRM before 6.3.4 allows a standard authenticated user to deploy a new WebApp WAR file to t… dimo-crm · yellowbox_crm 2020-01-21 high7.5 CVE-2019-14767 In DIMO YellowBox CRM before 6.3.4, Path Traversal in images/Apparence (dossier=../) and servletrecuperefichier (document=../) allows an unauthenticated user t… dimo-crm · yellowbox_crm 2020-01-21 medium6.5 CVE-2019-14766 Path Traversal in the file browser of DIMO YellowBox CRM before 6.3.4 allows a standard authenticated user to browse the server filesystem. dimo-crm · yellowbox_crm 2020-01-21 high8.8 CVE-2019-14765 Incorrect Access Control in AfficheExplorateurParam() in DIMO YellowBox CRM before 6.3.4 allows a standard authenticated user to use administrative controllers. dimo-crm · yellowbox_crm 2020-01-21 medium5.4 CVE-2019-1010147 Yellowfin Smart Reporting All Versions Prior to 7.3 is affected by: Incorrect Access Control - Privileges Escalation. bmc · remedy_smart_reporting, yellowfinbi · yellowfin_bi 2019-07-26 high8.8 CVE-2019-11886 The WaspThemes Visual CSS Style Editor (aka yellow-pencil-visual-theme-customizer) plugin before 7.2.1 for WordPress allows yp_option_update CSRF, as demonstra… yellowpencil · visual_css_style_editor 2019-05-13 medium6.5 CVE-2018-10758 The edit/ URI in Datenstrom Yellow 0.7.3 has CSRF via a delete action that can delete articles. datenstrom · yellow 2018-05-05 medium5.4 CVE-2018-10726 A stored XSS vulnerability was found in Datenstrom Yellow 0.7.3 via an "Edit page" action. datenstrom · yellow 2018-05-04

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.