NetSight

Security Dashboard

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

Reset
693 matching advisories · page 10 of 24Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2021-20279 The ID number user profile field required additional sanitizing to prevent a stored XSS risk in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17. composer · moodle/moodle 2021-03-15 medium5.3 CVE-2021-20185 It was found in Moodle before version 3.10.1, 3.9.4, 3.8.7 and 3.5.16 that messaging did not impose a character limit when sending messages, which could result… composer · moodle/moodle 2021-01-28 high7.2 CVE-2021-20187 It was found in Moodle before version 3.10.1, 3.9.4, 3.8.7 and 3.5.16 that it was possible for site administrators to execute arbitrary PHP scripts via a PHP i… composer · moodle/moodle 2021-01-28 medium5.4 CVE-2021-20186 It was found in Moodle before version 3.10.1, 3.9.4, 3.8.7 and 3.5.16 that if the TeX notation filter was enabled, additional sanitizing of TeX content was req… composer · moodle/moodle 2021-01-28 medium4.3 CVE-2021-20184 It was found in Moodle before version 3.10.1, 3.9.4 and 3.8.7 that a insufficient capability checks in some grade related web services meant students were able… composer · moodle/moodle 2021-01-28 medium5.4 CVE-2021-20183 It was found in Moodle before version 3.10.1 that some search inputs were vulnerable to reflected XSS due to insufficient escaping of search queries. composer · moodle/moodle 2021-01-28 medium6.1 CVE-2020-25627 The moodlenetprofile user profile field required extra sanitizing to prevent a stored XSS risk. composer · moodle/moodle 2020-12-09 medium6.1 CVE-2020-25631 A vulnerability was found in Moodle 3.9 to 3.9.1, 3.8 to 3.8.4 and 3.7 to 3.7.7 where it was possible to include JavaScript in a book's chapter title, which wa… composer · moodle/moodle 2020-12-08 high7.5 CVE-2020-25630 A vulnerability was found in Moodle where the decompressed size of zip files was not checked against available user quota before unzipping them, which could le… composer · moodle/moodle 2020-12-08 high8.8 CVE-2020-25629 A vulnerability was found in Moodle where users with "Log in as" capability in a course context (typically, course managers) may gain access to some site admin… composer · moodle/moodle 2020-12-08 medium6.1 CVE-2020-25628 Cross site-scripting (XSS) moodle composer · moodle/moodle 2020-12-08 medium5.3 CVE-2020-25703 The participants table download in Moodle always included user emails, but should have only done so when users' emails are not hidden. composer · moodle/moodle 2020-11-19 medium6.1 CVE-2020-25702 In Moodle, it was possible to include JavaScript when re-naming content bank items. composer · moodle/moodle 2020-11-19 medium5.3 CVE-2020-25701 If the upload course tool in Moodle was used to delete an enrollment method which did not exist or was not already enabled, the tool would erroneously enable t… composer · moodle/moodle 2020-11-19 medium6.5 CVE-2020-25700 In moodle, some database module web services allowed students to add entries within groups they did not belong to. composer · moodle/moodle 2020-11-19 high7.5 CVE-2020-25699 In moodle, insufficient capability checks could lead to users with the ability to course restore adding additional capabilities to roles within that course. composer · moodle/moodle 2020-11-19 high7.5 CVE-2020-25698 Users' enrollment capabilities were not being sufficiently checked in Moodle when they are restored into an existing course. composer · moodle/moodle 2020-11-19 high7.5 CVE-2020-10738 A flaw was found in Moodle versions 3.8 before 3.8.3, 3.7 before 3.7.6, 3.6 before 3.6.10, 3.5 before 3.5.12 and earlier unsupported versions. composer · moodle/moodle 2020-05-21 critical9.1 CVE-2019-14880 A vulnerability was found in Moodle versions 3.7 before 3.7.3, 3.6 before 3.6.7, 3.5 before 3.5.9 and earlier. composer · moodle/moodle 2020-03-31 medium6.1 CVE-2019-14884 A vulnerability was found in Moodle 3.7 before 3.73, 3.6 before 3.6.7 and 3.5 before 3.5.9, where a reflected XSS possible from some fatal error messages. composer · moodle/moodle 2020-03-18 medium5.3 CVE-2019-14883 A vulnerability was found in Moodle 3.6 before 3.6.7 and 3.7 before 3.7.3, where tokens used to fetch inline atachments in email notifications were not disable… composer · moodle/moodle 2020-03-18 medium6.1 CVE-2019-14882 A vulnerability was found in Moodle 3.7 to 3.7.3, 3.6 to 3.6.7, 3.5 to 3.5.9 and earlier where an open redirect existed in the Lesson edit page. composer · moodle/moodle 2020-03-18 medium6.1 CVE-2019-14881 A vulnerability was found in moodle 3.7 before 3.7.3, where there is blind XSS reflected in some locations where user email is displayed. composer · moodle/moodle 2020-03-18 high8.1 CVE-2020-1692 Moodle before version 3.7.2 is vulnerable to information exposure of service tokens for users enrolled in the same course. composer · moodle/moodle 2020-02-17 medium5.4 CVE-2019-18210 Persistent XSS in /course/modedit.php of Moodle through 3.7.2 allows authenticated users (Teacher and above) to inject JavaScript into the session of another u… composer · moodle/moodle 2020-02-11 medium5.4 CVE-2019-14879 A vulnerability was found in Moodle versions 3.7.x before 3.7.3, 3.6.x before 3.6.7 and 3.5.x before 3.5.9. composer · moodle/moodle 2020-01-07 high7.5 CVE-2012-1170 Moodle before 2.2.2 has an external enrolment plugin context check issue where capability checks are not thorough moodle · moodle, fedoraproject · fedora 2019-11-14 medium5.3 CVE-2012-1169 Moodle before 2.2.2 has Personal information disclosure, when administrative setting users name display is set to first name only full names are shown in page … moodle · moodle, fedoraproject · fedora 2019-11-14 medium4.3 CVE-2012-1161 Moodle before 2.2.2: Course information leak via hidden courses being displayed in tag search results moodle · moodle, fedoraproject · fedora 2019-11-14 low2.7 CVE-2012-1160 Moodle before 2.2.2 has a permission issue in Forum Subscriptions where unenrolled users can subscribe/unsubscribe via mod/forum/index.php moodle · moodle, fedoraproject · fedora 2019-11-14

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.