NetSight

Security Dashboard

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

Reset
44 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2026-2224 A vulnerability was detected in code-projects Online Reviewer System 1.0. fabian · online_reviewer_system 2026-02-09 low2.4 CVE-2026-2222 A weakness has been identified in code-projects Online Reviewer System 1.0. fabian · online_reviewer_system 2026-02-09 low2.4 CVE-2026-2214 A weakness has been identified in code-projects for Plugin 1.0. fabian · online_music_site 2026-02-09 low2.4 CVE-2026-2156 A weakness has been identified in code-projects Online Student Management System 1.0. fabian · online_student_management_system 2026-02-08 low3.5 CVE-2026-1421 A vulnerability has been found in code-projects Online Examination System 1.0. fabian · online_examination_system 2026-01-26 low3.5 CVE-2025-15052 A vulnerability was detected in code-projects Student Information System 1.0. fabian · student_information_system 2025-12-24 low2.4 CVE-2025-14663 A vulnerability was determined in code-projects Student File Management System 1.0. fabian · student_file_management_system 2025-12-14 low2.4 CVE-2025-14662 A vulnerability was found in code-projects Student File Management System 1.0. fabian · student_file_management_system 2025-12-14 low2.4 CVE-2025-14205 A vulnerability was found in code-projects Chamber of Commerce Membership Management System 1.0. fabian · chamber_of_commerce_membership_management_system 2025-12-08 low3.5 CVE-2025-13245 A vulnerability was identified in code-projects Student Information System 2.0. fabian · student_information_system 2025-11-16 low3.5 CVE-2025-13202 A security flaw has been discovered in code-projects Simple Cafe Ordering System 1.0. fabian · simple_cafe_ordering_system 2025-11-15 low2.4 CVE-2025-12282 A vulnerability was identified in code-projects Client Details System 1.0. fabian · client_details_system 2025-10-27 low2.4 CVE-2025-12281 A vulnerability was determined in code-projects Client Details System 1.0. fabian · client_details_system 2025-10-27 low2.4 CVE-2025-12280 A vulnerability was found in code-projects Client Details System 1.0. fabian · client_details_system 2025-10-27 low2.4 CVE-2025-12279 A vulnerability has been found in code-projects Client Details System 1.0. fabian · client_details_system 2025-10-27 low3.7 CVE-2025-11609 A flaw has been found in code-projects Hospital Management System 1.0. fabian · hospital_management_system 2025-10-11 low3.5 CVE-2025-11421 A flaw has been found in code-projects Voting System 1.0. fabian · voting_system 2025-10-08 low3.5 CVE-2025-11124 A vulnerability has been found in code-projects Project Monitoring System 1.0. fabian · project_monitoring_system 2025-09-28 low3.5 CVE-2025-10837 A security vulnerability has been detected in code-projects Simple Food Ordering System 1.0. fabian · simple_food_ordering_system 2025-09-23 low2.4 CVE-2025-9929 A weakness has been identified in code-projects Responsive Blog Site 1.0. fabian · responsive_blog_site 2025-09-04 low3.5 CVE-2025-8501 A vulnerability classified as problematic has been found in code-projects Human Resource Integrated System 1.0. fabian · human_resource_integrated_system 2025-08-03 low3.5 CVE-2025-7951 A vulnerability classified as problematic has been found in code-projects Public Chat Room 1.0. fabian · public_chat_room 2025-07-22 low3.5 CVE-2025-6849 A vulnerability, which was classified as problematic, was found in code-projects Simple Forum 1.0. fabian · simple_forum 2025-06-29 low2.4 CVE-2025-6778 A vulnerability, which was classified as problematic, was found in code-projects Food Distributor Site 1.0. fabian · food_distributor_site 2025-06-27 low3.5 CVE-2025-6353 A vulnerability classified as problematic was found in code-projects Responsive Blog 1.0. fabian · responsive_blog_site 2025-06-20 low2.4 CVE-2025-6347 A vulnerability was found in code-projects Responsive Blog 1.0/1.12.4/3.3.4. fabian · responsive_blog_site 2025-06-20 low3.5 CVE-2025-6340 A vulnerability classified as problematic has been found in code-projects School Fees Payment System 1.0. fabian · school_fees_payment_system 2025-06-20 low3.5 CVE-2025-4745 A vulnerability, which was classified as problematic, was found in code-projects Employee Record System 1.0. fabian · employee_record_system 2025-05-16 low3.5 CVE-2025-4744 A vulnerability, which was classified as problematic, has been found in code-projects Employee Record System 1.0. fabian · employee_record_system 2025-05-16 low3.5 CVE-2025-2673 A vulnerability classified as problematic has been found in code-projects Payroll Management System 1.0. fabian · payroll_management_system 2025-03-24

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.