NetSight

Security Dashboard

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

Reset
453 matching advisories · page 8 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2025-54134 HAX CMS NodeJS Application Has Improper Error Handling That Leads to Denial of Service npm · @haxtheweb/haxcms-nodejs 2025-07-21 high7.2 CVE-2025-54128 NodeJS version of HAX CMS Has Disabled Content Security Policy That Enables Cross-Site Scripting npm · @haxtheweb/haxcms-nodejs 2025-07-21 critical9.8 CVE-2025-54127 NodeJS version of HAX CMS Has Insecure Default Configuration That Leads to Unauthenticated Access npm · @haxtheweb/haxcms-nodejs 2025-07-21 critical GHSA-wcf2-599v-qjfq Malware in pyroscope-nodejsMalware npm · pyroscope-nodejs 2025-07-15 medium4.8 CVE-2025-53642 haxcms-nodejs and haxcms-php are backends for HAXcms. psu · haxcms-nodejs, psu · haxcms-php 2025-07-11 critical GHSA-xpgf-2764-m486 Malware in es6modules-nodejsMalware npm · es6modules-nodejs 2025-07-02 critical GHSA-rjq6-79fj-g32w Malware in gwnodejssectest1Malware npm · gwnodejssectest1 2025-06-10 high8.5 CVE-2025-49141 HaxCMS-PHP Command Injection Vulnerability npm · @haxtheweb/haxcms-nodejs 2025-06-09 medium5.3 CVE-2025-49139 @haxtheweb/haxcms-nodejs Iframe Phishing vulnerability npm · @haxtheweb/haxcms-nodejs 2025-06-09 high8.5 CVE-2025-49137 Hax CMS Stored Cross-Site Scripting vulnerability composer · elmsln/haxcms 2025-06-09 critical GHSA-8fqv-jr5x-q3hg Malware in logbin-nodejsMalware npm · logbin-nodejs 2025-05-27 critical GHSA-2f23-p99f-xrxq Malware in nodejs-fetch-proxyMalware npm · nodejs-fetch-proxy 2025-05-16 medium6.4 CVE-2025-47828 @lumieducation/h5p-server Fails to Sanitize Plain Text Strings npm · @lumieducation/h5p-server 2025-05-11 medium6.5 CVE-2025-47153 Certain build processes for libuv and Node.js for 32-bit systems, such as for the nodejs binary package through nodejs_20.19.0+dfsg-2_i386.deb for Debian GNU/L… 2025-05-01 low3.3 CVE-2025-46328 NodeJS Driver for Snowflake has race condition when checking access to Easy Logging configuration file npm · snowflake-sdk 2025-04-28 critical GHSA-4rp6-5vxg-6pqp Malware in rapyd-nodejsMalware npm · rapyd-nodejs 2025-04-03 critical GHSA-g5gg-gx7q-9pxg Malware in nodejs-websiteMalware npm · nodejs-website 2025-03-25 critical GHSA-4phv-fc37-7jch Malware in example-nodejs-expressMalware npm · example-nodejs-express 2025-03-11 critical GHSA-qfv2-vgfm-4v56 Malware in ee-server-auth-nodejsMalware npm · ee-server-auth-nodejs 2025-03-11 critical GHSA-c495-732j-2wc3 Malware in organizer-nodejsMalware npm · organizer-nodejs 2025-03-04 critical GHSA-v4hx-fq4j-7c4w Malware in auth0-nodejs-webapp-sample-new-testMalware npm · auth0-nodejs-webapp-sample-new-test 2025-02-28 critical GHSA-8q24-9r89-g6h8 Malware in nodejs-paypal-checkout-demoMalware npm · nodejs-paypal-checkout-demo 2025-02-10 critical GHSA-4xvh-qhcr-grcx Malware in sample-nodejs-vsk-with-admMalware npm · sample-nodejs-vsk-with-adm 2025-02-03 medium5.5 CVE-2025-23084 A vulnerability has been identified in Node.js, specifically affecting the handling of drive names in the Windows environment. nodejs · node.js 2025-01-28 critical GHSA-pfrh-cg2w-878w Malware in binance-toolbox-nodejsMalware npm · binance-toolbox-nodejs 2024-12-27 critical GHSA-fxg4-7x75-wwmf Malware in eslint-config-sunset-nodejsMalware npm · eslint-config-sunset-nodejs 2024-12-19 critical GHSA-qrg2-j2x5-v2xw Malware in cdp-agentkit-nodejsMalware npm · cdp-agentkit-nodejs 2024-12-19 critical GHSA-23c7-h5xw-5324 Malware in nodejs-prom-reporterMalware npm · nodejs-prom-reporter 2024-11-27 critical GHSA-75gh-7gwh-pjpx Malware in config-sdk-nodejsMalware npm · config-sdk-nodejs 2024-11-26 critical GHSA-mm7f-882r-wjw6 Malware in webhooks-resources-nodejs-serverMalware npm · webhooks-resources-nodejs-server 2024-10-29

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.