NetSight

Security Dashboard

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

Reset
375 matching advisories · page 10 of 13Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2022-2494 Cross-site Scripting (XSS) - Stored in GitHub repository openemr/openemr prior to 7.0.0. open-emr · openemr 2022-07-22 high8.1 CVE-2022-2493 Data Access from Outside Expected Data Manager Component in GitHub repository openemr/openemr prior to 7.0.0. open-emr · openemr 2022-07-22 medium6.5 CVE-2022-1461 Non Privilege User can Enable or Disable Registered in GitHub repository openemr/openemr prior to 6.1.0.1. open-emr · openemr 2022-04-25 high8.3 CVE-2022-1459 Non-Privilege User Can View Patient’s Disclosures in GitHub repository openemr/openemr prior to 6.1.0.1. open-emr · openemr 2022-04-25 medium5.4 CVE-2022-1458 Stored XSS Leads To Session Hijacking in GitHub repository openemr/openemr prior to 6.1.0.1. open-emr · openemr 2022-04-25 critical9.8 CVE-2020-13567 Multiple SQL injection vulnerabilities exist in phpGACL 3.3.7. open-emr · openemr, phpgacl_project · phpgacl 2022-04-18 medium5.4 CVE-2022-1181 Stored Cross Site Scripting in GitHub repository openemr/openemr prior to 6.0.0.2. open-emr · openemr 2022-03-30 low3.5 CVE-2022-1180 Reflected Cross Site Scripting in GitHub repository openemr/openemr prior to 6.0.0.4. open-emr · openemr 2022-03-30 medium5.4 CVE-2022-1179 Non-Privilege User Can Created New Rule and Lead to Stored Cross Site Scripting in GitHub repository openemr/openemr prior to 6.0.0.4. open-emr · openemr 2022-03-30 medium5.4 CVE-2022-1178 Stored Cross Site Scripting in GitHub repository openemr/openemr prior to 6.0.0.4. open-emr · openemr 2022-03-30 medium4.3 CVE-2022-1177 Accounting User Can Download Patient Reports in openemr in GitHub repository openemr/openemr prior to 6.1.0. open-emr · openemr 2022-03-30 medium5.4 CVE-2022-24643 A stored cross-site scripting (XSS) issue was discovered in the OpenEMR Hospital Information Management System version 6.0.0. open-emr · openemr 2022-03-25 medium4.3 CVE-2022-25041 OpenEMR v6.0.0 was discovered to contain an incorrect access control issue. open-emr · openemr 2022-03-23 high8.1 CVE-2022-25471 An Insecure Direct Object Reference (IDOR) vulnerability in OpenEMR 6.0.0 allows any authenticated attacker to access and modify unauthorized areas via a craft… open-emr · openemr 2022-03-03 medium6.5 CVE-2021-41843 An authenticated SQL injection issue in the calendar search function of OpenEMR 6.0.0 before patch 3 allows an attacker to read data from all tables of the dat… open-emr · openemr 2021-12-17 medium6.5 CVE-2021-40352 OpenEMR 6.0.0 has a pnotes_print.php?noteid= Insecure Direct Object Reference vulnerability via which an attacker can read the messages of all users. open-emr · openemr 2021-09-01 high8.1 CVE-2021-25923 In OpenEMR, versions 5.0.0 to 6.0.0.1 are vulnerable to weak password requirements as it does not enforce a maximum password length limit. open-emr · openemr 2021-06-24 high8.8 CVE-2021-32104 A SQL injection vulnerability exists (with user privileges) in interface/forms/eye_mag/save.php in OpenEMR 5.0.2.1. open-emr · openemr 2021-05-07 medium4.8 CVE-2021-32103 A Stored XSS vulnerability in interface/usergroup/usergroup_admin.php in OpenEMR before 5.0.2.1 allows a admin authenticated user to inject arbitrary web scrip… open-emr · openemr 2021-05-07 high8.8 CVE-2021-32102 A SQL injection vulnerability exists (with user privileges) in library/custom_template/ajax_code.php in OpenEMR 5.0.2.1. open-emr · openemr 2021-05-07 high8.2 CVE-2021-32101 The Patient Portal of OpenEMR 5.0.2.1 is affected by a incorrect access control system in portal/patient/_machine_config.php. open-emr · openemr 2021-05-07 high8.8 CVE-2020-13568 SQL injection vulnerability exists in phpGACL 3.3.7. open-emr · openemr, phpgacl_project · phpgacl 2021-04-13 high8.8 CVE-2020-13566 SQL injection vulnerabilities exist in phpGACL 3.3.7. open-emr · openemr, phpgacl_project · phpgacl 2021-04-13 medium6.1 CVE-2021-25922 In OpenEMR, versions 4.2.0 to 6.0.0 are vulnerable to Reflected Cross-Site-Scripting (XSS) due to user input not being validated properly. open-emr · openemr 2021-03-22 medium5.4 CVE-2021-25921 In OpenEMR, versions 2.7.3-rc1 to 6.0.0 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly in the `Allergies` s… open-emr · openemr 2021-03-22 medium6.5 CVE-2021-25920 In OpenEMR, versions v2.7.2-rc1 to 6.0.0 are vulnerable to Improper Access Control when creating a new user, which leads to a malicious user able to read and s… open-emr · openemr 2021-03-22 medium4.8 CVE-2021-25919 In OpenEMR, versions 5.0.2 to 6.0.0 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly. open-emr · openemr 2021-03-22 medium4.8 CVE-2021-25918 In OpenEMR, versions 5.0.2 to 6.0.0 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly and rendered in the TOTP… open-emr · openemr 2021-03-22 medium4.8 CVE-2021-25917 In OpenEMR, versions 5.0.2 to 6.0.0 are vulnerable to Stored Cross-Site-Scripting (XSS) due to user input not being validated properly and rendered in the U2F … open-emr · openemr 2021-03-22 high7.2 CVE-2020-29143 A SQL injection vulnerability in interface/reports/non_reported.php in OpenEMR before 5.0.2.5 allows a remote authenticated attacker to execute arbitrary SQL c… open-emr · openemr 2021-02-15

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.