NetSight

Security Dashboard

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

Reset
130 matching advisories · page 3 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.1 CVE-2025-68109 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 high8.8 CVE-2025-67877 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 medium5.4 CVE-2025-67876 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 medium5.4 CVE-2025-67875 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 high8.3 CVE-2025-66397 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 high7.2 CVE-2025-66396 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 high8.8 CVE-2025-66395 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 critical10.0 CVE-2025-62521 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-17 medium6.5 CVE-2025-67874 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-16 high7.2 CVE-2025-67751 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-16 high7.2 CVE-2025-66313 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2025-12-01 medium4.7 CVE-2025-11939 A vulnerability was determined in ChurchCRM up to 5.18.0. churchcrm · churchcrm 2025-10-19 medium5.6 CVE-2025-11938 A vulnerability was found in ChurchCRM up to 5.18.0. churchcrm · churchcrm 2025-10-19 high7.3 CVE-2025-11529 A security flaw has been discovered in ChurchCRM up to 5.18.0. churchcrm · churchcrm 2025-10-09 low3.7 CVE-2025-3954 A vulnerability, which was classified as problematic, has been found in ChurchCRM 5.16.0. churchcrm · churchcrm 2025-04-26 high7.2 CVE-2025-1135 A vulnerability exists in ChurchCRM 5.13.0. churchcrm · churchcrm 2025-02-19 high7.2 CVE-2025-1134 A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploiting a boolean-based and time-based blin… churchcrm · churchcrm 2025-02-19 high7.2 CVE-2025-1133 A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploiting a boolean-based blind SQL Injection… churchcrm · churchcrm 2025-02-19 high8.8 CVE-2025-1132 A time-based blind SQL Injection vulnerability exists in the ChurchCRM 5.13.0 and prior EditEventAttendees.php within the EN_tyid parameter. churchcrm · churchcrm 2025-02-19 medium4.8 CVE-2025-1024 A vulnerability exists in ChurchCRM 5.13.0 that allows an attacker to execute arbitrary JavaScript in a victim's browser via Reflected Cross-Site Scripting (XS… churchcrm · churchcrm 2025-02-19 critical9.8 CVE-2025-1023 A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploiting a time-based blind SQL Injection vu… churchcrm · churchcrm 2025-02-18 medium6.1 CVE-2025-0981 A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to hijack a user's session by exploiting a Stored Cross Site Scripting (XSS) vulne… churchcrm · churchcrm 2025-02-18 critical9.8 CVE-2024-53438 EventAttendance.php in ChurchCRM 5.7.0 is vulnerable to SQL injection. churchcrm · churchcrm 2024-11-22 high8.8 CVE-2024-39304 ChurchCRM is an open-source church management system. churchcrm · churchcrm 2024-07-26 medium5.4 CVE-2024-36647 A stored cross-site scripting (XSS) vulnerability in Church CRM v5.8.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected… churchcrm · churchcrm 2024-06-13 medium6.1 CVE-2024-25898 A XSS vulnerability was found in the ChurchCRM v.5.5.0 functionality, edit your event, where malicious JS or HTML code can be inserted in the Event Sermon fiel… churchcrm · churchcrm 2024-02-21 critical9.8 CVE-2024-25897 ChurchCRM 5.5.0 FRCatalog.php is vulnerable to Blind SQL Injection (Time-based) via the CurrentFundraiser GET parameter. churchcrm · churchcrm 2024-02-21 medium5.3 CVE-2024-25896 ChurchCRM 5.5.0 EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EID POST parameter. churchcrm · churchcrm 2024-02-21 medium6.1 CVE-2024-25895 A reflected cross-site scripting (XSS) vulnerability in ChurchCRM 5.5.0 allows remote attackers to inject arbitrary web script or HTML via the type parameter o… churchcrm · churchcrm 2024-02-21 critical9.8 CVE-2024-25894 ChurchCRM 5.5.0 /EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EventCount POST parameter. churchcrm · churchcrm 2024-02-21

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.