NetSight

Security Dashboard

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

Reset
170 matching advisories · page 4 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-cmq7-49g6-w9q4 Malware in grammy-telegram-bot-apiMalware npm · grammy-telegram-bot-api 2025-05-21 medium4.3 CVE-2025-48268 Missing Authorization vulnerability in Guru Team Bot for Telegram on WooCommerce bot-for-telegram-on-woocommerce allows Exploiting Incorrectly Configured Acces… Bot for Telegram on WooCommerce: from n/a through 2025-05-19 critical GHSA-fm5p-69px-frgp Malware in telegram-clientMalware npm · telegram-client 2025-04-03 medium6.4 CVE-2025-1450 The Floating Chat Widget: Contact Chat Icons, Telegram Chat, Line Messenger, WeChat, Email, SMS, Call Button, WhatsApp – Chaty plugin for WordPress is vulnerab… premio · floating_chat_widget 2025-02-27 critical GHSA-xx99-jgh5-7c4g Malware in telegram-bot-hoster3Malware npm · telegram-bot-hoster3 2025-02-17 critical GHSA-2hm8-478j-4j7x Malware in telegram-botsMalware npm · telegram-bots 2025-02-17 critical GHSA-gm2j-crm3-c77q Malware in telegram-bot-hoster2Malware npm · telegram-bot-hoster2 2025-02-17 critical GHSA-6qmq-hqfp-xp3c Malware in telegram-bot-hostMalware npm · telegram-bot-host 2025-02-17 critical GHSA-254x-fx4p-hw94 Malware in telegram-bot-hosterMalware npm · telegram-bot-hoster 2025-02-17 critical GHSA-9f6v-q9xg-cw83 Malware in telegram-bo-hostMalware npm · telegram-bo-host 2025-02-17 critical GHSA-qjpf-47v2-x5xh Malware in telegramclient-sdkMalware npm · telegramclient-sdk 2025-02-13 critical GHSA-8cqj-cjvv-x8pg Malware in telegramclient-utilsMalware npm · telegramclient-utils 2025-02-13 critical GHSA-2pq4-p69j-w4p2 Malware in telegram-utilMalware npm · telegram-util 2025-02-13 critical GHSA-4m92-phpr-hrwg Malware in node-telegram-bot-sdkMalware npm · node-telegram-bot-sdk 2025-02-13 critical GHSA-546h-h4rh-w6q9 Malware in node-telegram-sdkMalware npm · node-telegram-sdk 2025-02-13 medium6.8 CVE-2024-54916 An issue in the SharedConfig class of Telegram Android APK v.11.7.0 allows a physically proximate attacker to bypass authentication and escalate privileges by … 2025-02-11 critical GHSA-x88m-4mqg-qq5r Malware in telegramclientsMalware npm · telegramclients 2025-01-22 medium5.4 CVE-2024-38789 Cross-Site Request Forgery (CSRF) vulnerability in Marco Milesi Telegram Bot & Channel telegram-bot allows Cross Site Request Forgery.This issue affects Telegr… Telegram Bot & Channel: from n/a through 2025-01-02 medium6.4 CVE-2024-11885 The NinjaTeam Chat for Telegram plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'njtele_button shortcode in all versions up … 2024-12-24 high8.8 CVE-2024-53992 unzip-bot is a Telegram bot to extract various types of archives. 2024-12-02 medium6.4 CVE-2024-10390 The Elfsight Telegram Chat CC plugin for WordPress is vulnerable to unauthorized modification of data to a missing capability check on the 'updatePreferences' … 2024-11-18 medium5.4 CVE-2024-9629 The Contact Form 7 + Telegram plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the… 2024-10-28 medium5.4 CVE-2024-9630 The WPS Telegram Chat plugin for WordPress is vulnerable to authorization bypass due to a missing capability check when accessing messages in versions up to, a… 10web · wps_telegram_chat 2024-10-25 medium6.3 CVE-2024-9628 The WPS Telegram Chat plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'Wps_Te… 10web · wps_telegram_chat 2024-10-25 medium5.3 CVE-2024-9686 The Order Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nktgnfw_s… choplugins · order_notification_for_telegram 2024-10-25 high8.6 CVE-2024-9627 The TeploBot - Telegram Bot for WP plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'service_p… te-st · teplobot 2024-10-22 medium6.5 CVE-2024-9820 The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 3.0. dueclic · wp_2fa_with_telegram 2024-10-15 high8.8 CVE-2024-9687 The WP 2FA with Telegram plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 3.0. dueclic · wp_2fa_with_telegram 2024-10-15 high8.8 CVE-2024-9821 The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'stm_wpcf… 2024-10-12 medium4.3 CVE-2024-9685 The Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nftb_test_actio… andreamarinucci · notification_for_telegram 2024-10-10

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.