NetSight

Security Dashboard

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

Reset
21 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.3 CVE-2026-130674 Craft CMS from 5.0.0 before 5.11.4 contains an incomplete blocklist fix that allows attackers who can author entry type title formats to write arbitrary files … craftcms · cms, statamic · CMS 3 days ago critical9.3 CVE-2026-130675 Craft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform() that allows attackers to instantiate… craftcms · cms, statamic · CMS 3 days ago critical9.3 CVE-2026-115934 An unauthenticated SQL injection can occur on the front end of any site that uses craft.search to perform a search, allowing stacked query execution and enabli… craftcms · cms, statamic · CMS 12 days ago critical9.3 CVE-2026-124427 Craft CMS from 5.0.0 before 5.11.2 contains an authorization bypass vulnerability that allows anonymous GraphQL clients to read out-of-scope section entries vi… craftcms · cms, statamic · CMS 13 days ago critical9.3 CVE-2026-123488 Craft CMS 4.0.0 before 4.18.9 and 5.0.0 before 5.11.2 contains an unauthenticated SQL injection vulnerability in the element search endpoint because the attrib… craftcms · cms, statamic · CMS 15 days ago critical4.3 GHSA-4hc4-qjfx-wjf3 Duplicate Advisory: Craft CMS: Authorization bypass: view-only Categories user can modify category structure via structures/move-element composer · craftcms/cms 2026-08-11 critical9.1 GHSA-wg23-69c2-gjc8 Craft CMS: Passkey login accepts replayed WebAuthn assertions composer · craftcms/cms 2026-08-07 critical9.2 CVE-2026-55791 Craft CMS: Blind SSRF and Arbitrary JavaScript Injection via Host Header Poisoning in actionResourceJs composer · craftcms/cms 2026-06-19 critical9.8 CVE-2026-32267 Craft CMS Vulnerable to Privilege Escalation/Bypass through UsersController->actionImpersonateWithToken() composer · craftcms/cms 2026-03-16 critical9.1 CVE-2026-28783 Craft CMS has Twig Function Blocklist Bypass composer · craftcms/cms 2026-03-03 critical9.4 CVE-2026-28697 Craft CMS Vulnerable to Authenticated RCE via "craft.app.fs.write()" in Twig Templates composer · craftcms/cms 2026-03-03 critical9.8 CVE-2020-37071 CraftCMS 3 vCard Plugin 1.0.0 contains a deserialization vulnerability that allows unauthenticated attackers to execute arbitrary PHP code through a crafted pa… 2026-02-03 critical9.1 CVE-2025-68456 Unauthenticated Craft CMS users can trigger a database backup composer · craftcms/cms 2026-01-05 critical9.8 CVE-2025-52122 Freeform 5.0.0 to before 5.10.16, a plugin for CraftCMS, contains an Server-side template injection (SSTI) vulnerability, resulting in arbitrary code injection… composer · solspace/craft-freeform 2025-08-27 critical10.0 CVE-2025-32432 Craft CMS Code Injection VulnerabilityExploited composer · craftcms/cms 2025-04-25 critical9.8 CVE-2024-56145 Craft CMS has potential RCE when PHP `register_argc_argv` config setting is enabledExploited composer · craftcms/cms 2024-12-18 critical9.8 CVE-2024-37843 Craft CMS SQL injection vulnerability via the GraphQL API endpoint composer · craftcms/cms 2024-06-25 critical10.0 CVE-2023-41892 Craft CMS Remote Code Execution vulnerability composer · craftcms/cms 2023-09-13 critical9.8 CVE-2021-27903 Craft CMS Remote Code Injection composer · craftcms/cms 2021-06-30 critical9.8 CVE-2020-9757 SEOmatic for CraftCMS allows Server-Side Template Injection composer · nystudio107/craft-seomatic 2020-03-04 critical9.8 CVE-2019-15929 Craft CMS possibility of brute force attempts composer · craftcms/cms 2019-10-24

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.