NetSight

Security Dashboard

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

Reset
42 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2026-116385 A security vulnerability has been detected in Bdtask Garage 24 Garage Management Software 1.0. 26 days ago medium5.3 CVE-2026-116384 A weakness has been identified in Bdtask Garage 24 Garage Management Software 1.0. Bdtask · Garage 24 Garage Management Software 26 days ago medium6.3 CVE-2026-10172 A security flaw has been discovered in Bdtask Multi-Store Inventory Management System 1.0. 2026-05-31 medium4.7 CVE-2026-10155 A vulnerability was found in Bdtask Multi-Store Inventory Management System 1.0. 2026-05-31 high7.1 CVE-2019-25505 Tradebox 5.4 contains an SQL injection vulnerability that allows authenticated attackers to manipulate database queries by injecting SQL code through the symbo… bdtask · tradebox 2026-03-04 medium4.3 CVE-2026-1600 A vulnerability was identified in Bdtask Bhojon All-In-One Restaurant Management System up to 20260116. bdtask · bhojon 2026-01-29 medium4.3 CVE-2026-1599 A vulnerability was determined in Bdtask Bhojon All-In-One Restaurant Management System up to 20260116. bdtask · bhojon 2026-01-29 low3.5 CVE-2026-1598 A vulnerability was found in Bdtask Bhojon All-In-One Restaurant Management System up to 20260116. bdtask · bhojon 2026-01-29 medium6.3 CVE-2026-1597 A vulnerability has been found in Bdtask SalesERP up to 20260116. bdtask · saleserp 2026-01-29 medium5.1 CVE-2025-40679 HTML Injection vulnerability in Isshue by Bdtask, consisting os an HTML injection due to a lack os proper validation of user input by sending a POST request to… 2026-01-20 medium4.8 CVE-2021-47769 Isshue Shopping Cart 3.5 contains a persistent cross-site scripting vulnerability in title input fields across stock, customer, and invoice modules. bdtask · isshue 2026-01-15 medium4.3 CVE-2025-13239 A security vulnerability has been detected in Bdtask/CodeCanyon Isshue Multi Store eCommerce Shopping Cart Solution 5. bdtask · isshue 2025-11-16 medium6.3 CVE-2025-13238 A weakness has been identified in Bdtask Flight Booking Software 4. bdtask · flight_booking_software 2025-11-16 low2.4 CVE-2025-13186 A weakness has been identified in Bdtask/CodeCanyon Isshue Multi Store eCommerce Shopping Cart Solution up to 4.0. bdtask · isshue 2025-11-14 medium4.7 CVE-2025-13185 A security flaw has been discovered in Bdtask/CodeCanyon News365 up to 7.0.3. bdtask · news365 2025-11-14 low3.5 CVE-2025-13180 A vulnerability was found in Bdtask/CodeCanyon Wholesale Inventory Control and Inventory Management System up to 20250320. bdtask · wholesale 2025-11-14 medium4.3 CVE-2025-13179 A vulnerability has been found in Bdtask/CodeCanyon Wholesale Inventory Control and Inventory Management System up to 20250320. bdtask · wholesale 2025-11-14 low3.5 CVE-2025-13178 A flaw has been found in Bdtask/CodeCanyon SalesERP up to 20250728. bdtask · saleserp 2025-11-14 medium4.3 CVE-2025-13177 A vulnerability was detected in Bdtask/CodeCanyon SalesERP up to 20250728. bdtask · saleserp 2025-11-14 medium4.3 CVE-2025-12288 A vulnerability was detected in Bdtask Pharmacy Management System up to 9.4. bdtask · pharmacare 2025-10-27 medium4.7 CVE-2025-12287 A security vulnerability has been detected in Bdtask Wholesale Inventory Control and Inventory Management System up to 20251013. bdtask · wholesale 2025-10-27 medium6.3 CVE-2025-12223 A vulnerability was detected in Bdtask Flight Booking Software up to 3.1. bdtask · flight_booking_software 2025-10-27 medium6.3 CVE-2025-12222 A security vulnerability has been detected in Bdtask Flight Booking Software up to 3.1. bdtask · flight_booking_software 2025-10-27 medium4.3 CVE-2024-3151 A vulnerability, which was classified as problematic, was found in Bdtask Multi-Store Inventory Management System up to 20240325. bdtask · m-store 2024-04-02 low2.4 CVE-2024-2998 A vulnerability was found in Bdtask Multi-Store Inventory Management System up to 20240320. bdtask · multi_store_inventory_management_system 2024-03-27 low2.4 CVE-2024-2997 A vulnerability was found in Bdtask Multi-Store Inventory Management System up to 20240320. bdtask · multi_store_inventory_management_system 2024-03-27 low2.4 CVE-2024-2996 A vulnerability was found in Bdtask Multi-Store Inventory Management System up to 20240320. bdtask · multi_store_inventory_management_system 2024-03-27 medium4.3 CVE-2024-2639 A vulnerability was found in Bdtask Wholesale Inventory Management System up to 20240311. 2024-03-19 low3.8 CVE-2024-2317 A vulnerability was found in Bdtask Hospital AutoManager up to 20240227 and classified as problematic. bdtask · hospital_automanager 2024-03-08 medium4.3 CVE-2024-2316 A vulnerability has been found in Bdtask Hospital AutoManager up to 20240227 and classified as problematic. bdtask · hospital_automanager 2024-03-08

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.