NetSight

Security Dashboard

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

Reset
27 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2026-0580 A vulnerability was found in SourceCodester API Key Manager App 1.0. remyandrade · api_key_manager_app 2026-01-05 low3.5 CVE-2025-13349 A vulnerability has been found in SourceCodester Student Grades Management System 1.0. remyandrade · student_grades_management_system 2025-11-18 low2.4 CVE-2025-12332 A flaw has been found in SourceCodester Student Grades Management System 1.0. remyandrade · student_grades_management_system 2025-10-28 low2.4 CVE-2025-11485 A vulnerability was determined in SourceCodester Student Grades Management System 1.0. remyandrade · student_grades_management_system 2025-10-08 low3.5 CVE-2025-5628 A vulnerability, which was classified as problematic, has been found in SourceCodester Food Menu Manager 1.0. remyandrade · food_menu_manager 2025-06-05 low3.5 CVE-2025-1905 A vulnerability, which was classified as problematic, was found in SourceCodester Employee Management System 1.0. remyandrade · employee_management_system 2025-03-04 low3.5 CVE-2024-8337 A vulnerability, which was classified as problematic, has been found in SourceCodester Contact Manager with Export to VCF 1.0. remyandrade · contact_manager_with_export_to_vcf 2024-08-30 low3.5 CVE-2024-7948 A vulnerability classified as problematic was found in SourceCodester Accounts Manager App 1.0. remyandrade · accounts_manager_app 2024-08-20 low3.5 CVE-2024-7749 A vulnerability, which was classified as problematic, was found in SourceCodester Accounts Manager App 1.0. remyandrade · accounts_manager_app 2024-08-13 low3.5 CVE-2024-7660 A vulnerability has been found in SourceCodester File Manager App 1.0 and classified as problematic. remyandrade · file_manager_app 2024-08-12 low3.5 CVE-2024-2935 A vulnerability, which was classified as problematic, has been found in SourceCodester Todo List in Kanban Board 1.0. remyandrade · todo_list_in_kanban_board 2024-03-27 low3.5 CVE-2024-2553 A vulnerability, which was classified as problematic, was found in SourceCodester Product Review Rating System 1.0. remyandrade · product_review\/rating_system 2024-03-17 low3.5 CVE-2024-2075 A vulnerability was found in SourceCodester Daily Habit Tracker 1.0. remyandrade · daily_habit_tracker 2024-03-01 low3.5 CVE-2024-2072 A vulnerability, which was classified as problematic, was found in SourceCodester Flashcard Quiz App 1.0. remyandrade · flashcard_quiz_app 2024-03-01 low3.5 CVE-2024-2071 A vulnerability, which was classified as problematic, has been found in SourceCodester FAQ Management System 1.0. remyandrade · faq_management_system 2024-03-01 low3.5 CVE-2024-2070 A vulnerability classified as problematic was found in SourceCodester FAQ Management System 1.0. remyandrade · faq_management_system 2024-03-01 low3.5 CVE-2024-2068 A vulnerability was found in SourceCodester Computer Inventory System 1.0. remyandrade · computer_inventory_system 2024-03-01 low2.4 CVE-2024-2066 A vulnerability was found in SourceCodester Computer Inventory System 1.0. remyandrade · computer_inventory_system 2024-03-01 low3.5 CVE-2024-2065 A vulnerability was found in SourceCodester Barangay Population Monitoring System up to 1.0 and classified as problematic. remyandrade · barangay_population_monitoring_system 2024-03-01 low2.4 CVE-2024-1269 A vulnerability has been found in SourceCodester Product Management System 1.0 and classified as problematic. remyandrade · product_management_system 2024-02-07 low3.5 CVE-2024-1215 A vulnerability was found in SourceCodester CRUD without Page Reload 1.0. remyandrade · crud_without_page_reload\/refresh 2024-02-03 low3.5 CVE-2023-7059 A vulnerability was found in SourceCodester School Visitor Log e-Book 1.0. remyandrade · school_visitor_log_e-book 2023-12-22 low3.5 CVE-2023-6473 A vulnerability, which was classified as problematic, was found in SourceCodester Online Quiz System 1.0. remyandrade · online_quiz_system 2023-12-02 low3.5 CVE-2023-6463 A vulnerability has been found in SourceCodester User Registration and Login System 1.0 and classified as problematic. remyandrade · user_registration_and_login_system 2023-12-01 low3.5 CVE-2023-6462 A vulnerability, which was classified as problematic, was found in SourceCodester User Registration and Login System 1.0. remyandrade · user_registration_and_login_system 2023-12-01 low3.5 CVE-2023-6440 A vulnerability was found in SourceCodester Book Borrower System 1.0 and classified as problematic. remyandrade · book_borrower_system 2023-11-30 low3.5 CVE-2023-5791 A vulnerability, which was classified as problematic, was found in SourceCodester Sticky Notes App 1.0. remyandrade · sticky_notes_app 2023-10-26

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.