NetSight

Security Dashboard

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

Reset
1,160 matching advisories · page 4 of 39Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2024-44659 PHPGurukul Online Shopping Portal 2.0 is vulnerable to SQL Injection via the email parameter in forgot-password.php. phpgurukul · online_shopping_portal 2025-11-17 medium4.6 CVE-2024-46335 PHPGurukul Complaint Management System 2.0 is vulnerble to Cross Site Scripting (XSS) via the fromdate and todate parameters in between-date-userreport.php. phpgurukul · complaint_management_system 2025-11-17 medium6.5 CVE-2024-44663 PHPGurukul Online Shopping Portal 2.0 is vulnerable to SQL Injection via the product parameter in search-result.php. phpgurukul · online_shopping_portal 2025-11-17 medium6.5 CVE-2024-44662 PHPGurukul Online Shopping Portal 2.0 is vulnerable to SQL Injection via the username parameter in the admin page. phpgurukul · online_shopping_portal 2025-11-17 medium6.5 CVE-2024-44660 PHPGurukul Online Shopping Portal 2.0 is vulnerable to SQL Injection via the fullname, emailid, and contactno parameters in login.php. phpgurukul · online_shopping_portal 2025-11-17 medium6.5 CVE-2024-44658 PHPGurukul Complaint Management System 2.0 is vulnerable to SQL Injection via the subcategory and category parameters in subcategory.php. phpgurukul · complaint_management_system 2025-11-17 medium6.1 CVE-2024-44655 PHPGurukul Complaint Management System 2.0 is vulnerable to Cross Site Scripting (XSS) via the search parameter in user-search.php. phpgurukul · complaint_management_system 2025-11-17 medium6.5 CVE-2024-44654 PHPGurukul Complaint Management System 2.0 is vulnerable to SQL Injection via the email and mobileno parameters in reset-password.php. phpgurukul · complaint_management_system 2025-11-17 medium6.5 CVE-2024-44657 PHPGurukul Complaint Management System 2.0 is vulnerable to SQL Injection via the fromdate and todate parameters in between-date-userreport.php. phpgurukul · complaint_management_system 2025-11-17 medium6.5 CVE-2024-44648 PHPGurukul Small CRM 3.0 is vulnerable to SQL Injection via id and adminremark parameters in quote-details.php. phpgurukul · small_crm 2025-11-17 medium6.1 CVE-2024-44647 PHPGurukul Small CRM 3.0 is vulnerable to Cross Site Scripting (XSS) via the aremark parameter in manage-tickets.php. phpgurukul · small_crm 2025-11-17 medium6.5 CVE-2024-44644 PHPGurukul Small CRM 3.0 is vulnerable to SQL Injection via the frm_id and aremark parameters in manage-tickets.php. phpgurukul · small_crm 2025-11-17 medium6.5 CVE-2024-44641 PHPGurukul Small CRM 3.0 is vulnerable to SQL Injection via the oldpass parameter in change-password.php. phpgurukul · small_crm 2025-11-17 high7.3 CVE-2025-13247 A security flaw has been discovered in PHPGurukul Tourism Management System 1.0. phpgurukul · tourism_management_system 2025-11-16 medium6.5 CVE-2024-55016 PHPGurukul Student Record Management System 3.20 is vulnerable to SQL Injection via the id and password parameters in login.php. phpgurukul · student_record_system 2025-11-14 medium6.5 CVE-2024-44640 PHPGurukul Student Record System 3.20 is vulnerable to SQL Injection via the course-short, course-full, and cdate parameters in add-course.php. phpgurukul · student_record_system 2025-11-14 medium6.5 CVE-2024-44639 PHPGurukul Student Record System 3.20 is vulnerable to SQL Injection via the sub1, sub2, sub3, sub4, and course-short parameters in add-subject.php. phpgurukul · student_record_system 2025-11-14 medium6.5 CVE-2024-44636 PHPGurukul Student Record System 3.20 is vulnerable to SQL Injection via the adminname and aemailid parameters in /admin-profile.php. phpgurukul · student_record_system 2025-11-14 medium6.1 CVE-2024-44635 PHPGurukul Student Record System 3.20 is vulnerable to Cross Site Scripting (XSS) via adminname and aemailid parameters in /admin-profile.php. phpgurukul · student_record_system 2025-11-14 medium6.5 CVE-2024-44633 PHPGurukul Student Record System 3.20 is vulnerable to SQL Injection via the currentpassword parameter in change-password.php. phpgurukul · student_record_system 2025-11-14 medium6.5 CVE-2024-44632 PHPGurukul Student Record System 3.20 is vulnerable to SQL Injection via the id and emailid parameters in password-recovery.php. phpgurukul · student_record_system 2025-11-14 medium6.5 CVE-2024-44630 Multiple parameters in register.php in PHPGurukul Student Record System 3.20 are vulnerable to SQL injection. phpgurukul · student_record_system 2025-11-14 medium5.4 CVE-2025-50363 Phpgurukul Maid Hiring Management System 1.0 is vulnerable to Cross Site Scripting (XSS) in /maid-hiring.php va the name field. phpgurukul · maid_hiring_management_system 2025-11-03 low3.7 CVE-2025-12616 A vulnerability was detected in PHPGurukul News Portal 1.0. phpgurukul · news_portal 2025-11-03 medium5.0 CVE-2025-12615 A security vulnerability has been detected in PHPGurukul News Portal 1.0. phpgurukul · news_portal 2025-11-03 low2.4 CVE-2025-12312 A flaw has been found in PHPGurukul Curfew e-Pass Management System 1.0. phpgurukul · curfew_e-pass_management_system 2025-10-27 low2.4 CVE-2025-12311 A vulnerability was detected in PHPGurukul Curfew e-Pass Management System 1.0. phpgurukul · curfew_e-pass_management_system 2025-10-27 low2.4 CVE-2025-12303 A flaw has been found in PHPGurukul Curfew e-Pass Management System 1.0. phpgurukul · curfew_e-pass_management_system 2025-10-27 medium6.1 CVE-2025-61255 Bank Locker Management System by PHPGurukul is affected by a Cross-Site Scripting (XSS) vulnerability via the /search parameter, where unsanitized input allows… phpgurukul · bank_locker_management_system 2025-10-21 high7.3 CVE-2025-11507 A weakness has been identified in PHPGurukul Beauty Parlour Management System 1.1. phpgurukul · beauty_parlour_management_system 2025-10-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.