NetSight

Security Dashboard

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

Reset
34 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2025-63564 SQL injection vulnerability in Moodle Socialwall plugin v.3.0 through v.3.3 allows an attacker to execute arbitrary code via crafted HTTP requests 59 days ago critical GHSA-x9mq-fvhh-w497 Malicious code in ezmoodle (npm)Malware npm · ezmoodle 2026-09-10 critical9.3 CVE-2026-54733 The Microsoft 365 and Microsoft Entra ID Plugins for Moodle provide Office 365 and Azure Active Directory integration for Moodle. 2026-07-16 critical9.6 CVE-2026-30884 mdjnelson/moodle-mod_customcert is a Moodle plugin for creating dynamically generated certificates with complete customization via the web browser. 2026-03-18 critical GHSA-cj86-xpcp-75mh Malware in moodle-core-widget-focusaftercloseMalware npm · moodle-core-widget-focusafterclose 2025-09-05 critical GHSA-qfhf-r8pc-w4vv Malware in moodle-core-lockscrollMalware npm · moodle-core-lockscroll 2025-09-05 critical GHSA-r5vh-r28r-fqv9 Malware in moodle-core-tooltipMalware npm · moodle-core-tooltip 2025-09-05 critical GHSA-p882-228v-j78r Malware in moodle-core_filepickerMalware npm · moodle-core_filepicker 2025-09-05 critical GHSA-2389-q2fj-cvjc Malware in moodle-core-notification-dialogueMalware npm · moodle-core-notification-dialogue 2025-09-05 critical9.8 CVE-2024-33999 Moodle Improper Input Validation composer · moodle/moodle 2024-05-31 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 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 critical9.1 CVE-2022-45152 Moodle blind Server-Side Request Forgery (SSRF) vulnerability in LTI provider library composer · moodle/moodle 2022-11-25 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 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 critical9.8 CVE-2022-0332 A flaw was found in Moodle in versions 3.11 to 3.11.4. composer · moodle/moodle 2022-01-25 critical9.8 CVE-2021-3943 A flaw was found in Moodle in versions 3.11 to 3.11.3, 3.10 to 3.10.7, 3.9 to 3.9.10 and earlier unsupported versions. composer · moodle/moodle 2021-11-22 critical9.1 CVE-2021-21809 A command execution vulnerability exists in the default legacy spellchecker plugin in Moodle 3.10. composer · moodle/moodle 2021-06-23 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 critical9.8 CVE-2019-15536 The Acclaim block plugin before 2019-06-26 for Moodle allows SQL Injection via delete_records. youracclaim · acclaim 2019-08-23 critical10.0 CVE-2019-3809 A flaw was found in Moodle versions 3.1 to 3.1.15 and earlier unsupported versions. composer · moodle/moodle 2019-03-25 critical9.8 CVE-2017-2641 In Moodle 2.x and 3.x, SQL injection can occur via user preferences. composer · moodle/moodle 2017-03-26 critical10.0 CVE-2006-4935 The Database module in Moodle before 1.6.2 does not properly handle uploaded files, which has unspecified impact and remote attack vectors. moodle · moodle 2006-09-23 critical10.0 CVE-2006-4936 Moodle before 1.6.2 does not properly validate the module instance id when creating a course module object, which has unspecified impact and remote attack vect… composer · moodle/moodle 2006-09-23 critical10.0 CVE-2005-2247 Multiple unknown vulnerabilities in Moodle before 1.5.1 have unknown impact and attack vectors. moodle · moodle 2005-07-12

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.