NetSight

Security Dashboard

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

Reset
144 matching advisories · page 3 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.9 CVE-2023-38048 A BOLA vulnerability in GET, PUT, DELETE /providers/{providerId} allows a low privileged user to fetch, modify or delete a privileged user (provider). easyappointments · easyappointments 2024-07-09 high8.5 CVE-2023-38047 A BOLA vulnerability in GET, PUT, DELETE /categories/{categoryId} allows a low privileged user to fetch, modify or delete the category of any user (including a… easyappointments · easyappointments 2024-07-09 medium4.4 CVE-2023-52884 In the Linux kernel, the following vulnerability has been resolved: Input: cyapa - add missing input core locking to suspend/resume functions Grab input->mutex… linux · linux_kernel 2024-06-21 high7.4 CVE-2024-33831 A stored cross-site scripting (XSS) vulnerability in the Advanced Expectation - Response module of yapi v1.10.2 allows attackers to execute arbitrary web scrip… 2024-04-30 medium6.3 CVE-2023-32295 Missing Authorization vulnerability in Alex Tselegidis Easy!Appointments.This issue affects Easy!Appointments: from n/a through 1.3.3. easyappointments · easy\!appointments 2024-04-11 medium6.4 CVE-2024-0698 The Easy!Appointments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'easyappointments' shortcode in all versions up to, an… easyappointments · easy\!appointments 2024-03-05 critical9.8 CVE-2023-39852 Doctormms v1.0 was discovered to contain a SQL injection vulnerability via the $userid parameter at myAppoinment.php. doctor_appointment_system_project · doctor_appointment_system 2023-08-15 medium6.3 CVE-2023-3700 Easy!Appointments Improper Access Control vulnerability composer · alextselegidis/easyappointments 2023-07-17 medium6.3 CVE-2023-3568 Open Redirect in GitHub repository alextselegidis/easyappointments prior to 1.5.0. fossbilling · fossbilling 2023-07-10 high8.8 CVE-2023-2105 alextselegidis/easyappointments Session Fixation vulnerability composer · alextselegidis/easyappointments 2023-04-15 medium5.4 CVE-2023-2104 alextselegidis/easyappointments Improper Access Control vulnerability composer · alextselegidis/easyappointments 2023-04-15 medium5.4 CVE-2023-2103 alextselegidis/easyappointments vulnerable to Stored Cross-site Scripting composer · alextselegidis/easyappointments 2023-04-15 medium6.8 CVE-2023-2102 alextselegidis/easyappointments vulnerable to Stored Cross-site Scripting composer · alextselegidis/easyappointments 2023-04-15 high7.3 CVE-2023-1367 Code Injection in alextselegidis/easyappointments composer · alextselegidis/easyappointments 2023-03-13 critical9.8 CVE-2023-1269 Easy!Appointments uses hard-coded credentials composer · alextselegidis/easyappointments 2023-03-08 high7.5 GHSA-wxwq-525w-hcqx Yapscan Denial of Service vulnerability in report server go · github.com/fkie-cad/yapscan 2023-03-03 medium5.4 CVE-2021-36686 Cross-site Scripting in yapi-vendor npm · yapi-vendor 2023-01-26 high7.5 GHSA-9h6h-9g78-86f7 Yapscan's report receiver server vulnerable to path traversal and log injection go · github.com/fkie-cad/yapscan 2022-12-29 low2.4 CVE-2022-4731 A vulnerability, which was classified as problematic, was found in myapnea up to 29.0.x. myapnea · myapnea 2022-12-25 medium5.5 CVE-2022-20511 In getNearbyAppStreamingPolicy of DevicePolicyManagerService.java, there is a missing permission check. google · android 2022-12-16 critical GHSA-5jfw-qm5c-2p6m Malware in myapp-by-7h3n00bMalware npm · myapp-by-7h3n00b 2022-09-27 critical GHSA-4pmg-252f-jrmg Malware in connecthistoryapifallbaccMalware npm · connecthistoryapifallbacc 2022-08-19 critical GHSA-p9r8-2p3v-x46c Malware in zuyapvkdcmxoiwblMalware npm · zuyapvkdcmxoiwbl 2022-07-11 high8.8 CVE-2022-1397 Privilege escalation in easyappointments composer · alextselegidis/easyappointments 2022-05-10 critical9.1 CVE-2022-0482 Exposure of Private Personal Information to an Unauthorized Actor in alextselegidis/easyappointments composer · alextselegidis/easyappointments 2022-03-09 high7.5 CVE-2022-0732 The backend infrastructure shared by multiple mobile device monitoring services does not adequately authenticate or authorize API requests, creating an IDOR (I… 1byte · copy9, 1byte · exactspy, 1byte · fonetracker +6 2022-02-24 high8.1 CVE-2021-20873 Yappli is an application development platform which provides the function to access a requested URL using Custom URL Scheme. yappli · yappli 2021-12-28 medium6.1 CVE-2021-31803 cPanel before 94.0.3 allows self-XSS via EasyApache 4 Save Profile (SEC-581). cpanel · cpanel 2021-04-26 medium5.1 CVE-2021-27884 Weak JSON Web Token in yapi-vendor npm · yapi-vendor 2021-03-01 medium4.3 CVE-2020-2251 Passwords transmitted in plain text by Jenkins ReadyAPI Functional Testing Plugin maven · org.jenkins-ci.plugins:soapui-pro-functional-testing 2020-09-01

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.