NetSight

Security Dashboard

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

Reset
693 matching advisories · page 4 of 24Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2025-3627 Moodle makes some user data available before completing second factor with MFA enabled composer · moodle/moodle 2025-04-25 high7.1 CVE-2025-3625 A security vulnerability was discovered in Moodle that can allow hackers to gain access to sensitive information about students and prevent them from logging i… 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 high7.5 CVE-2025-32044 Moodle allows unauthenticated REST API user data exposure composer · moodle/moodle 2025-04-25 medium4.3 CVE-2025-3634 A security vulnerability was discovered in Moodle that allows students to enroll themselves in courses without completing all the necessary safety checks. composer · moodle/moodle 2025-04-25 high8.1 CVE-2025-26533 Moodle has a SQL injection risk in course search module list filter composer · moodle/moodle 2025-02-24 low3.1 CVE-2025-26532 Moodle allows teachers to evade trusttext config when restoring glossary entries composer · moodle/moodle 2025-02-24 low3.1 CVE-2025-26531 Moodle has an IDOR in badges allows disabling of arbitrary badges composer · moodle/moodle 2025-02-24 high8.3 CVE-2025-26530 Moodle allows reflected XSS via question bank filter composer · moodle/moodle 2025-02-24 high8.3 CVE-2025-26529 Moodle has a stored XSS risk in admin live log composer · moodle/moodle 2025-02-24 low3.4 CVE-2025-26528 Moodle has a stored XSS in ddimageortext question type composer · moodle/moodle 2025-02-24 medium5.3 CVE-2025-26527 Moodle's non-searchable tags can still be discovered on the tag search page and in the tags block composer · moodle/moodle 2025-02-24 medium6.5 CVE-2025-26526 Moodle's feedback response viewing and deletions did not respect Separate Groups mode composer · moodle/moodle 2025-02-24 high8.6 CVE-2025-26525 Moodle has an arbitrary file read risk through pdfTeX composer · moodle/moodle 2025-02-24 medium4.3 CVE-2024-48899 Moodle IDOR when accessing list of course badges composer · moodle/moodle 2024-11-20 medium5.4 CVE-2024-45691 Moodle Lesson activity password bypass through PHP loose comparison composer · moodle/moodle 2024-11-20 high7.5 CVE-2024-45690 Moodle IDOR when deleting OAuth2 linked accounts composer · moodle/moodle 2024-11-20 medium6.5 CVE-2024-45689 Moodle allows users to retrieve information they did not have permission to access composer · moodle/moodle 2024-11-20 medium4.3 CVE-2024-48901 moodle: IDOR when fetching report schedules composer · moodle/moodle 2024-11-18 medium6.5 CVE-2024-48898 moodle: Some users can delete audiences of other reports composer · moodle/moodle 2024-11-18 medium6.5 CVE-2024-48897 moodle: IDOR in edit/delete RSS feed composer · moodle/moodle 2024-11-18 medium4.3 CVE-2024-48896 Moodle leaks user names composer · moodle/moodle 2024-11-18 medium5.3 CVE-2024-48900 Moodle IDOR when accessing list of badge recipients composer · moodle/moodle 2024-11-13 medium5.4 CVE-2024-43439 Moodle reflected XSS via H5P error message composer · moodle/moodle 2024-11-11 medium5.4 CVE-2024-43437 Moodle Cross-site Scripting vulnerability composer · moodle/moodle 2024-11-11 medium5.3 CVE-2024-43435 Moodle has insufficient capability checks composer · moodle/moodle 2024-11-11 medium5.3 CVE-2024-43433 Moodle's user/power level management inconsistent with suspended users composer · moodle/moodle 2024-11-11 medium5.3 CVE-2024-43432 Moodle authorization headers preserved between "emulated redirects" composer · moodle/moodle 2024-11-11 medium5.3 CVE-2024-43430 Moodle has insufficient access control composer · moodle/moodle 2024-11-11 medium5.3 CVE-2024-43429 Moodle has user information visibility control issues in gradebook reports composer · moodle/moodle 2024-11-11

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.