NetSight

Security Dashboard

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

Reset
112 matching advisories · page 2 of 4Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2024-43425 Moodle Remote Code Execution vulnerability composer · moodle/moodle 2024-11-07 high8.8 CVE-2024-38276 Moodle CSRF risks due to misuse of confirm_sesskey composer · moodle/moodle 2024-06-18 high7.5 CVE-2024-38275 Moodle HTTP authorization header is preserved between "emulated redirects" composer · moodle/moodle 2024-06-18 high7.5 CVE-2024-34009 Moodle ReCAPTCHA can be bypassed on the login page composer · moodle/moodle 2024-05-31 high8.8 CVE-2024-34008 Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk. composer · moodle/moodle 2024-05-31 high8.8 CVE-2024-34007 The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF. composer · moodle/moodle 2024-05-31 high6.5 CVE-2024-34005 Moodle Authenticated LFI risk in some misconfigured shared hosting environments composer · moodle/moodle 2024-05-31 high6.5 CVE-2024-34002 Moodle Authenticated LFI risk in some misconfigured shared hosting environments composer · moodle/moodle 2024-05-31 high8.4 CVE-2024-34001 Actions in the admin preset tool did not include the necessary token to prevent a CSRF risk. composer · moodle/moodle 2024-05-31 high8.8 CVE-2024-25982 The link to update all installed language packs did not include the necessary token to prevent a CSRF risk. composer · moodle/moodle 2024-02-19 high7.5 CVE-2024-25978 Uncontrolled Resource Consumption in moodle composer · moodle/moodle 2024-02-19 high8.8 CVE-2023-5540 Moodle Code Injection vulnerability composer · moodle/moodle 2023-11-09 high7.5 CVE-2023-35133 Moodle vulnerable to Server Side Request Forgery composer · moodle/moodle 2023-06-22 high7.3 CVE-2023-30944 The vulnerability was found Moodle which exists due to insufficient sanitization of user-supplied data in external Wiki method for listing pages. composer · moodle/moodle 2023-05-02 high8.8 CVE-2023-28335 The link to reset all templates of a database activity did not include the necessary token to prevent a CSRF risk. composer · moodle/moodle 2023-03-23 high8.8 CVE-2023-28329 Moodle SQL Injection vulnerability composer · moodle/moodle 2023-03-23 high7.5 CVE-2021-36396 In Moodle, insufficient redirect handling made it possible to blindly bypass cURL blocked hosts/allowed ports restrictions, resulting in a blind SSRF risk. composer · moodle/moodle 2023-03-06 high7.5 CVE-2021-36395 In Moodle, the file repository's URL parsing required additional recursion handling to mitigate the risk of recursion denial of service. composer · moodle/moodle 2023-03-06 high8.2 CVE-2023-23923 The vulnerability was found Moodle which exists due to insufficient limitations on the "start page" preference. composer · moodle/moodle 2023-02-17 high8.8 CVE-2022-2986 Enabling and disabling installed H5P libraries did not include the necessary token to prevent a CSRF risk. composer · moodle/moodle 2022-10-06 high7.1 CVE-2022-40313 Moodle Stored Cross-site Scripting and page denial of service composer · moodle/moodle 2022-09-30 high7.2 CVE-2020-1756 In Moodle before 3.8.2, 3.7.5, 3.6.9 and 3.5.11, insufficient input escaping was applied to the PHP unit webrunner admin tool. moodle · moodle 2022-08-16 high7.5 CVE-2020-14322 In Moodle before 3.9.1, 3.8.4, 3.7.7 and 3.5.13, yui_combo needed to limit the amount of files it can load to help mitigate the risk of denial of service. moodle · moodle 2022-08-16 high8.8 CVE-2020-14321 In Moodle before 3.9.1, 3.8.4, 3.7.7 and 3.5.13, teachers of a course were able to assign themselves the manager role within that course. composer · moodle/moodle 2022-08-16 high7.5 CVE-2022-35650 The vulnerability was found in Moodle, occurs due to input validation error when importing lesson questions. composer · moodle/moodle 2022-07-25 high7.5 CVE-2022-28986 LMS Doctor Simple 2 Factor Authentication Plugin For Moodle Affected: 2021072900 has an Insecure direct object references (IDOR) vulnerability, which allows re… lmsdoctor · 2_factor_authentication 2022-05-10 high8.8 CVE-2022-0983 SQL Injection in Moodle composer · moodle/moodle 2022-03-25 high7.5 CVE-2021-32476 A denial-of-service risk was identified in the draft files area, due to it not respecting user file upload limits. composer · moodle/moodle 2022-03-11 high7.2 CVE-2021-32474 An SQL injection risk existed on sites with MNet enabled and configured, via an XML-RPC call from the connected peer host. composer · moodle/moodle 2022-03-11 high8.8 CVE-2022-0335 A flaw was found in Moodle in versions 3.11 to 3.11.4, 3.10 to 3.10.8, 3.9 to 3.9.11 and earlier unsupported versions. composer · moodle/moodle 2022-01-25

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.