NetSight

Security Dashboard

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

Reset
86 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.1 CVE-2026-133479 A vulnerability was detected in WebKul QloApps up to 1.8.0. Affected by this vulnerability is the... WebKul · QloApps, Webkul · QloApps 2 days ago medium6.1 CVE-2024-58401 Bagisto 2.1.0 before 2.2.1 contains a client-side template injection vulnerability in the search page where the 'query' parameter is rendered unescaped inside … Webkul · Bagisto, n/a · Bagisto 3 days ago medium5.4 CVE-2026-121733 Bagisto before 2.4.5 contains a stored cross-site scripting vulnerability that allows authenticated customers to upload HTML files via the RMA send-message end… Webkul · Bagisto, n/a · Bagisto 18 days ago medium6.9 CVE-2026-116745 QloApps through 1.7.0 contains an information disclosure vulnerability in OrderConfirmationController::init() that allows unauthenticated attackers to obtain g… qloapps · qloapps, Webkul · QloApps 26 days ago low3.7 CVE-2026-112193 A vulnerability was detected in Webkul Aureus ERP up to 1.6.0. Webkul Aureus ERP 33 days ago medium5.3 CVE-2026-112190 A security vulnerability has been detected in Webkul Aureus ERP up to 1.6.0. Webkul Aureus ERP 33 days ago low2.7 CVE-2026-101139 A vulnerability was detected in Webkul Bagisto up to 2.4.6/2.5.0-beta4. Webkul Bagisto 54 days ago high8.8 CVE-2026-79411 Incorrect privilege assignment in the admin user-management component of Webkul Bagisto 2.4.9 allows an authenticated backend user holding only the settings.us… 2026-09-15 high8.1 CVE-2026-79410 Improper validation of the quantity parameter in the add-to-cart path of Webkul Bagisto v2.4.9 allows authenticated attackers to reduce their order total below… 2026-09-15 medium6.5 CVE-2026-79409 An issue in Webkul Bagisto 2.4.9 allows a remote attacker to obtain sensitive information via the add-to-cart API and the downloadable fulfilment components. 2026-09-15 high7.2 CVE-2026-75498 Webkul QloApps does not validate request parameters before a database query. 2026-08-25 high7.2 CVE-2026-75497 Webkul QloApps does not validate request parameters before a database query. 2026-08-25 high7.2 CVE-2026-75496 Webkul QloApps does not perform proper validation on uploaded file extensions or MIME types before moving the file to a publicly accessible directory. 2026-08-25 medium4.3 CVE-2026-75082 A flaw has been found in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-18 medium4.3 CVE-2026-75081 A vulnerability was detected in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-18 medium4.7 CVE-2026-19997 A security flaw has been discovered in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-17 medium4.3 CVE-2026-19996 A vulnerability was identified in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-17 low3.5 CVE-2026-19995 A vulnerability was determined in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-17 medium6.3 CVE-2026-19994 A vulnerability was found in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-17 medium4.3 CVE-2026-19993 A vulnerability has been found in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-17 medium4.3 CVE-2026-19838 A security vulnerability has been detected in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-14 low2.7 CVE-2026-19837 A weakness has been identified in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-14 medium4.3 CVE-2026-19836 A security flaw has been discovered in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-14 low3.8 CVE-2026-19835 A vulnerability was identified in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-14 medium4.7 CVE-2026-19834 A vulnerability was determined in Webkul Bagisto up to 2.4.4. Webkul Bagisto 2026-08-14 high8.2 CVE-2017-20262 Joomla! webkul · ajax_quiz 2026-06-19 high8.2 CVE-2026-25861 QloApps through 1.7.0, fixed in commit 64e9722, contains a weak cryptographic algorithm vulnerability that allows attackers to compromise user credentials by e… QloApps · QloApps, Webkul · QloApps 2026-06-02 medium5.4 CVE-2026-36341 Webkul Krayin CRM is Vulnerable to Cross-Site Scripting in the /admin/activities/create endpoint composer · krayin/laravel-crm 2026-05-07 high8.1 CVE-2026-38532 A Broken Object-Level Authorization (BOLA) in the /Contact/Persons/PersonController.php endpoint of Webkul Krayin CRM v2.2.x allows authenticated attackers to … composer · krayin/laravel-crm 2026-04-14 high8.1 CVE-2026-38530 A Broken Object-Level Authorization (BOLA) in the /Controllers/Lead/LeadController.php endpoint of Webkul Krayin CRM v2.2.x allows authenticated attackers to a… composer · krayin/laravel-crm 2026-04-14

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.