NetSight

Security Dashboard

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

Reset
74 matching advisories · page 2 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2026-56382 Craft CMS (composer package craftcms/cms) versions >= 5.5.0 and <= 5.9.13 contain a remote code execution vulnerability in the FieldsController::actionRenderCa… composer · craftcms/cms 2026-06-21 medium4.3 CVE-2026-49288 Statamic CMS: Missing authorization on Control Panel fieldtype endpoints allows disclosure of restricted resources composer · statamic/cms 2026-06-19 high7.4 CVE-2026-49287 Statamic CMS's unsafe method invocation via collection sorting allows data destruction composer · statamic/cms 2026-06-19 medium5.4 CVE-2026-45660 Statamic is a Laravel and Git powered content management system (CMS). composer · statamic/cms 2026-05-18 medium5.3 CVE-2026-44306 Statamic CMS vulnerable to email enumeration via forgot password endpoint composer · statamic/cms 2026-05-06 high8.1 CVE-2026-41175 Statamic: Unsafe method invocation via query value resolution allows data destruction composer · statamic/cms 2026-04-16 medium5.4 CVE-2026-33887 Statamic allows unauthorized content access through missing authorization in its revision controllers composer · statamic/cms 2026-03-26 medium6.5 CVE-2026-33886 Statamic's sensitive configuration values are exposed to content editors via Antlers-enabled fields composer · statamic/cms 2026-03-26 medium6.1 CVE-2026-33885 Statamic has an Open Redirect on unauthenticated endpoints via URL parsing differential composer · statamic/cms 2026-03-26 medium4.3 CVE-2026-33884 Statamic's live preview token bypasses content protection for unrelated entries composer · statamic/cms 2026-03-26 medium6.1 CVE-2026-33883 Statamic has Reflected XSS via unescaped redirect parameter in its password reset form tag composer · statamic/cms 2026-03-26 medium6.5 CVE-2026-33882 Statamic is a Laravel and Git powered content management system (CMS). composer · statamic/cms 2026-03-26 medium5.3 CVE-2026-56385 Duplicate Advisory: Craft CMS: Authorized asset "preview file" requests bypass allows users without asset access to retrieve private preview metadata composer · craftcms/cms 2026-03-26 medium4.3 CVE-2026-33177 Statamic is missing authorization check on taxonomy term creation via fieldtype composer · statamic/cms 2026-03-18 medium4.3 CVE-2026-33171 Statamic has a path traversal in file dictionary fieldtype composer · statamic/cms 2026-03-18 high8.7 CVE-2026-33172 Statamic has Stored XSS via SVG Sanitization Bypass composer · statamic/cms 2026-03-18 medium5.4 CVE-2026-32612 Statamic vulnerable to privilege escalation via stored cross-site scripting composer · statamic/cms 2026-03-13 medium4.6 CVE-2026-56381 Craft CMS from version 5.0.0-RC1 contains a stored cross-site scripting vulnerability in the User Permissions page where user group names are rendered without … composer · craftcms/cms 2026-03-11 medium4.6 CVE-2026-56393 Craft CMS 4.x (>= 4.0.0-RC1, < 4.17.0-beta.1) and 5.x (>= 5.0.0-RC1, < 5.9.0-beta.1) contain multiple stored cross-site scripting vulnerabilities where setting… composer · craftcms/cms 2026-03-03 high8.7 CVE-2026-28426 Statamic vulnerable to privilege escalation via stored cross-site scripting composer · statamic/cms 2026-02-27 high8.0 CVE-2026-28425 Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs composer · statamic/cms 2026-02-27 medium6.5 CVE-2026-28424 Statamic's missing authorization allows access to email addresses composer · statamic/cms 2026-02-27 medium6.8 CVE-2026-28423 Statamic Vulnerable to Server-Side Request Forgery via Glide composer · statamic/cms 2026-02-27 high8.8 CVE-2026-27939 Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass composer · statamic/cms 2026-02-27 medium4.6 CVE-2026-56383 Craft CMS contains a stored cross-site scripting (XSS) vulnerability in the editableTable.twig component when using the 'Row Heading' column type. composer · craftcms/cms 2026-02-25 critical9.3 CVE-2026-27593 Statamic is vulnerable to account takeover via password reset link injection composer · statamic/cms 2026-02-24 high8.1 CVE-2026-27196 Statamic affected by privilege escalation via stored cross-site scripting composer · statamic/cms 2026-02-19 high8.7 CVE-2026-25759 Statamic CMS vulnerable to privilege escalation via stored cross-site scripting composer · statamic/cms 2026-02-11 medium4.3 CVE-2026-25633 Statamic CMS's missing authorization allows access to assets composer · statamic/cms 2026-02-11 high8.0 CVE-2025-64112 Statamic Vulnerable to Superadmin Account Takeover via Stored Cross-Site Scripting and Lack of Proper X-CSRF-TOKEN Server-Side Validation composer · statamic/cms 2025-10-30

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.