NetSight

Security Dashboard

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

Reset
693 matching advisories · page 8 of 24Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 medium4.3 CVE-2022-40316 Moodle No groups filtering in H5P activity attempts report composer · moodle/moodle 2022-09-30 critical9.8 CVE-2022-40315 Moodle Minor SQL injection risk in admin user browsing composer · moodle/moodle 2022-09-30 critical9.8 CVE-2022-40314 A remote code execution risk when restoring backup files originating from Moodle 1.9 was identified. composer · moodle/moodle 2022-09-30 high7.1 CVE-2022-40313 Moodle Stored Cross-site Scripting and page denial of service composer · moodle/moodle 2022-09-30 medium4.3 CVE-2021-40695 Moodle Exposure of Sensitive Information to an Unauthorized Actor composer · moodle/moodle 2022-09-29 medium4.9 CVE-2021-40694 Moodle Improper Encoding or Escaping of Output composer · moodle/moodle 2022-09-29 medium6.5 CVE-2021-40693 Moodle type juggling vulnerability composer · moodle/moodle 2022-09-29 medium4.3 CVE-2021-40692 Moodle Incorrect Authorization composer · moodle/moodle 2022-09-29 medium4.3 CVE-2021-40691 Moodle Improper Authentication composer · moodle/moodle 2022-09-29 medium5.4 CVE-2021-36568 In certain Moodle products after creating a course, it is possible to add in a arbitrary "Topic" a resource, in this case a "Database" with the type "Text" whe… composer · moodle/moodle 2022-09-13 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 medium5.3 CVE-2020-1755 In Moodle before 3.8.2, 3.7.5, 3.6.9 and 3.5.11, X-Forwarded-For headers could be used to spoof a user's IP, in order to bypass remote address checks. 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 medium6.1 CVE-2020-14320 In Moodle before 3.9.1, 3.8.4 and 3.7.7, the filter in the admin task log required extra sanitizing to prevent a reflected XSS risk. composer · moodle/moodle 2022-08-16 medium4.3 CVE-2020-1754 In Moodle before 3.8.2, 3.7.5, 3.6.9 and 3.5.11, users viewing the grade history report without the 'access all groups' capability were not restricted to viewi… moodle · moodle 2022-08-05 medium5.4 CVE-2020-1691 In Moodle 3.8, messages required extra sanitizing before updating the conversation overview, to prevent the risk of stored cross-site scripting. composer · moodle/moodle 2022-08-05 medium6.1 CVE-2022-35653 A reflected XSS issue was identified in the LTI module of Moodle. composer · moodle/moodle 2022-07-25 medium6.1 CVE-2022-35652 An open redirect issue was found in Moodle due to improper sanitization of user-supplied data in mobile auto-login feature. composer · moodle/moodle 2022-07-25 medium6.1 CVE-2022-35651 A stored XSS and blind SSRF vulnerability was found in Moodle, occurs due to insufficient sanitization of user-supplied data in the SCORM track details. composer · moodle/moodle 2022-07-25 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 critical9.8 CVE-2022-35649 The vulnerability was found in Moodle, occurs due to improper input validation when parsing PostScript code. composer · moodle/moodle 2022-07-25 critical9.8 CVE-2022-30600 A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout threshold being bypassed. composer · moodle/moodle 2022-05-18 critical9.8 CVE-2022-30599 A flaw was found in moodle where an SQL injection risk was identified in Badges code relating to configuring criteria. composer · moodle/moodle 2022-05-18 medium4.3 CVE-2022-30598 A flaw was found in moodle where global search results could include author information on some activities where a user may not otherwise have access to it. composer · moodle/moodle 2022-05-18 medium5.3 CVE-2022-30597 A flaw was found in moodle where the description user field was not hidden when being set as a hidden user field. composer · moodle/moodle 2022-05-18 medium5.4 CVE-2022-30596 A flaw was found in moodle where ID numbers displayed when bulk allocating markers to assignments required additional sanitizing to prevent a stored XSS risk. composer · moodle/moodle 2022-05-18 medium6.5 CVE-2022-28601 A Two-Factor Authentication (2FA) bypass vulnerability in "Simple 2FA Plugin for Moodle" by LMS Doctor allows remote attackers to overwrite the phone number us… lmsdoctor · 2_factor_authentication 2022-05-10 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

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.