NetSight

Security Dashboard

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

Reset
504 matching advisories · page 2 of 17Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-102577 A flaw was found in Moodle. moodle · moodle 53 days ago medium6.1 CVE-2026-65882 Joomla Extension - joomdle.com - Reflected XSS vulnerability in Joomdle < 3.1.1 - The goto url parameter of the moodle wrapper endpoint allowed a reflected XSS… Joomdle 2026-07-28 medium6.1 CVE-2022-50943 Moodle LMS 4.0 contains a cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts by submitting payloads through t… moodle · moodle 2026-05-10 medium6.5 CVE-2026-26047 Moodle TeX formula editor is vulnerable to DoS through lack of execution time limits composer · moodle/moodle 2026-02-21 medium4.3 CVE-2025-67857 Moodle Inserts Sensitive Information Into Sent Data composer · moodle/moodle 2026-02-03 medium5.4 CVE-2025-67856 Moodle has an authorization logic flaw composer · moodle/moodle 2026-02-03 medium5.4 CVE-2025-67855 Moodle vulnerable to Cross-site Scripting composer · moodle/moodle 2026-02-03 medium6.1 CVE-2025-67851 Moodle formula injection vulnerability composer · moodle/moodle 2026-02-03 medium5.4 CVE-2025-62401 An issue in Moodle’s timed assignment feature allowed students to bypass the time restriction, potentially giving them more time than allowed to complete an as… composer · moodle/moodle 2025-10-23 medium4.3 CVE-2025-62400 Moodle exposed the names of hidden groups to users who had permission to create calendar events but not to view hidden groups. composer · moodle/moodle 2025-10-23 medium5.4 CVE-2025-62398 A serious authentication flaw allowed attackers with valid credentials to bypass multi-factor authentication under certain conditions, potentially compromising… composer · moodle/moodle 2025-10-23 medium5.3 CVE-2025-62397 The router’s inconsistent response to invalid course IDs allowed attackers to infer which course IDs exist, potentially aiding reconnaissance. moodle · moodle 2025-10-23 medium5.3 CVE-2025-62396 Moodle's error handling leads to sensitive information disclosure composer · moodle/moodle 2025-10-23 medium4.3 CVE-2025-62395 A flaw in the cohort search web service allowed users with permissions in lower contexts to access cohort information from the system context, revealing restri… moodle · moodle 2025-10-23 medium4.3 CVE-2025-62394 Moodle failed to verify enrolment status correctly when sending quiz notifications. composer · moodle/moodle 2025-10-23 medium4.3 CVE-2025-62393 A flaw was found in the course overview output function where user access permissions were not fully enforced. composer · moodle/moodle 2025-10-23 medium4.3 CVE-2025-60511 Moodle OpenAI Chat Block plugin 3.0.1 (2025021700) suffers from an Insecure Direct Object Reference (IDOR) vulnerability due to insufficient validation of the … 2025-10-21 medium5.4 CVE-2025-60506 Moodle PDF Annotator plugin v1.5 release 9 allows stored cross-site scripting (XSS) via the Public Comments feature. 2025-10-21 medium4.2 CVE-2025-53021 Moodle Session Fixation allows unauthenticated users to hijack sessions via sesskey parameter composer · moodle/moodle 2025-06-24 medium6.1 CVE-2025-34032 A reflected cross-site scripting (XSS) vulnerability exists in the Moodle LMS Jmol plugin version 6.1 and prior via the data parameter in jsmol.php. geoffrowland · jmol 2025-06-24 medium4.3 CVE-2025-4513 A vulnerability classified as problematic was found in Catalyst User Key Authentication Plugin 20220819 on Moodle. 2025-05-10 medium4.3 CVE-2025-3647 Moodle allows IDOR when accessing the cohorts report composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3645 Moodle has an IDOR in messaging web service which allows access to some user details composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3644 Moodle's AJAX section delete does not respect course_can_delete_section() composer · moodle/moodle 2025-04-25 medium5.4 CVE-2025-3643 Moodle has reflected Cross-site Scripting risk in policy tool composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3640 Moodle has an IDOR in web service which allows users enrolled in a course to access some details of other users composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3636 Moodle allows IDOR in RSS block, which allows access to additional RSS feeds composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3628 Moodle reveals student identities through assignment submissions search on anonymous submissions composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3627 Moodle makes some user data available before completing second factor with MFA enabled composer · moodle/moodle 2025-04-25 medium5.3 CVE-2025-32045 A flaw has been identified in Moodle where insufficient capability checks in certain grade reports allowed users without the necessary permissions to access hi… composer · moodle/moodle 2025-04-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.