NetSight

Security Dashboard

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

Reset
693 matching advisories · page 7 of 24Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2023-28336 Moodle may allow teachers to access the names of users they could not otherwise access composer · moodle/moodle 2023-03-23 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 medium4.3 CVE-2023-28334 Moodle may allow authenticated users to enumerate other user's names via learning plans page composer · moodle/moodle 2023-03-23 critical9.8 CVE-2023-28333 The Mustache pix helper contained a potential Mustache injection risk if combined with user input (note: This did not appear to be implemented/exploitable anyw… composer · moodle/moodle 2023-03-23 medium6.1 CVE-2023-28332 If the algebra filter was enabled but not functional (eg the necessary binaries were missing from the server), it presented an XSS risk. composer · moodle/moodle 2023-03-23 medium6.1 CVE-2023-28331 Moodle vulnerable to Cross-site Scripting composer · moodle/moodle 2023-03-23 medium6.5 CVE-2023-28330 Moodle arbitrary file read vulnerability composer · moodle/moodle 2023-03-23 high8.8 CVE-2023-28329 Moodle SQL Injection vulnerability composer · moodle/moodle 2023-03-23 medium4.3 CVE-2023-1402 Moodle may display roles to users who don't have access to them composer · moodle/moodle 2023-03-23 medium5.3 CVE-2021-36403 In Moodle, in some circumstances, email notifications of messages could have the link back to the original message hidden by HTML, which may pose a phishing ri… composer · moodle/moodle 2023-03-06 medium5.3 CVE-2021-36402 In Moodle, Users' names required additional sanitizing in the account confirmation email, to prevent a self-registration phishing risk. composer · moodle/moodle 2023-03-06 medium4.8 CVE-2021-36401 In Moodle, ID numbers exported in HTML data formats required additional sanitizing to prevent a local stored XSS risk. composer · moodle/moodle 2023-03-06 medium5.3 CVE-2021-36400 In Moodle, insufficient capability checks made it possible to remove other users' calendar URL subscriptions. composer · moodle/moodle 2023-03-06 medium5.4 CVE-2021-36399 In Moodle, ID numbers displayed in the quiz override screens required additional sanitizing to prevent a stored XSS risk. composer · moodle/moodle 2023-03-06 medium5.4 CVE-2021-36398 In moodle, ID numbers displayed in the web service token list required additional sanitizing to prevent a stored XSS risk. composer · moodle/moodle 2023-03-06 medium5.3 CVE-2021-36397 In Moodle, insufficient capability checks meant message deletions were not limited to the current user. composer · moodle/moodle 2023-03-06 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 critical9.8 CVE-2021-36394 In Moodle, a remote code execution risk was identified in the Shibboleth authentication plugin. composer · moodle/moodle 2023-03-06 critical9.8 CVE-2021-36393 In Moodle, an SQL injection risk was identified in the library fetching a user's recent courses. composer · moodle/moodle 2023-03-06 critical9.8 CVE-2021-36392 In Moodle, an SQL injection risk was identified in the library fetching a user's enrolled courses. 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 medium6.1 CVE-2023-23922 The vulnerability was found Moodle which exists due to insufficient sanitization of user-supplied data in blog search. composer · moodle/moodle 2023-02-17 medium6.1 CVE-2023-23921 The vulnerability was found Moodle which exists due to insufficient sanitization of user-supplied data in some returnurl parameters. composer · moodle/moodle 2023-02-17 medium6.5 CVE-2022-39183 Moodle Plugin - SAML Auth may allow Open Redirect through unspecified vectors. moodle · saml_authentication 2023-01-12 medium4.3 CVE-2020-36633 A vulnerability was found in moodle-block_sitenews 1.0. moodle-block_sitenews_project · moodle-block_sitenews 2022-12-27 critical9.1 CVE-2022-45152 Moodle blind Server-Side Request Forgery (SSRF) vulnerability in LTI provider library composer · moodle/moodle 2022-11-25 medium5.4 CVE-2022-45151 The stored-XSS vulnerability was discovered in Moodle which exists due to insufficient sanitization of user-supplied data in several "social" user profile fiel… composer · moodle/moodle 2022-11-23 medium6.1 CVE-2022-45150 A reflected cross-site scripting vulnerability was discovered in Moodle. composer · moodle/moodle 2022-11-23 medium5.4 CVE-2022-45149 A vulnerability was found in Moodle which exists due to insufficient validation of the HTTP request origin in course redirect URL. composer · moodle/moodle 2022-11-23

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.