NetSight

Security Dashboard

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

Reset
294 matching advisories · page 2 of 10Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2024-47047 powermail TYPO3 extension has Insecure Direct Object Reference composer · in2code/powermail 2024-09-17 high8.1 GHSA-f777-f784-36gm TYPO3 Security Misconfiguration in Install Tool Cookie composer · typo3/cms, composer · typo3/cms, composer · typo3/cms 2024-06-07 high8.8 GHSA-8h4m-r4wm-xj7r TYPO3 Arbitrary Code Execution via File List Module composer · typo3/cms, composer · typo3/cms 2024-06-07 high7.5 GHSA-g585-crjf-vhwq TYPO3 Denial of Service in Frontend Record Registration composer · typo3/cms, composer · typo3/cms 2024-06-07 high7.3 GHSA-c5mj-39cf-3pp5 TYPO3 Security Misconfiguration for Backend User Accounts composer · typo3/cms, composer · typo3/cms 2024-06-07 high8.1 GHSA-hh95-5xm5-v8v7 TYPO3 CMS Possible Insecure Deserialization in Extbase Request Handling composer · typo3/cms, composer · typo3/cms 2024-06-07 high GHSA-xjw3-5r5c-m5ph typo3 Security fix for Flow Swift Mailer package composer · typo3/swiftmailer, composer · typo3/swiftmailer 2024-06-05 high GHSA-g4xv-r3qw-v3q2 typo3 Information Disclosure Security Note composer · typo3/neos, composer · typo3/neos, composer · typo3/neos +6 2024-06-05 high GHSA-vh6j-wv25-8qxr Flow Bugfix Releases for Entity Security composer · typo3/flow, composer · typo3/flow, composer · typo3/flow +2 2024-06-05 high GHSA-4542-p56h-8xww Cross-Site Scripting (XSS) vulnerabilities in Neos composer · typo3/neos, composer · typo3/neos 2024-06-05 high GHSA-ppgf-8745-8pgx Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS composer · typo3/cms, composer · typo3/cms, composer · typo3/cms 2024-06-05 high8.8 GHSA-7qwg-fcpw-xg5g Privilege Escalation & SQL Injection in TYPO3 CMS composer · typo3/cms, composer · typo3/cms 2024-06-05 high GHSA-g4pf-3jvq-2gcw TYPO3 Remote Code Execution in third party library swiftmailer composer · typo3/cms, composer · typo3/cms, composer · typo3/cms 2024-06-05 high GHSA-8h28-f46f-m87h Insecure Deserialization in TYPO3 CMS composer · typo3/cms, composer · typo3/cms 2024-06-05 high GHSA-qffc-gwpp-m2xr XML External Entity (XXE) Processing in TYPO3 Core composer · typo3/cms, composer · typo3/cms 2024-06-04 high GHSA-9895-53fc-98v2 TYPO3 SQL Injection in dbal composer · typo3/cms 2024-06-03 high7.1 GHSA-r9vc-jfmh-6j48 TYPO3 frontend login vulnerable to Session Fixation composer · typo3/cms, composer · typo3/cms 2024-05-30 high8.8 GHSA-4r76-xr68-w7m7 TYPO3 may allow editors to change, create, or delete metadata of files not within their file mounts composer · typo3/cms, composer · typo3/cms 2024-05-30 high GHSA-p84g-j2gh-83g3 TYPO3 possible cache poisoning on the homepage when anchors are used composer · typo3/cms, composer · typo3/cms 2024-05-30 high8.1 GHSA-45xg-4w5x-j429 TYPO3 Arbitrary Shell Execution in Swiftmailer library composer · typo3/cms, composer · typo3/cms, composer · typo3/cms +1 2024-05-30 high8.1 GHSA-5h5v-m596-r6rf TYPO3 Possible Insecure Deserialization in Extbase Request Handling composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high8.8 GHSA-x428-565f-8xj2 TYPO3 Arbitrary Code Execution and Cross-Site Scripting in Backend API composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high8.2 GHSA-82vp-jr39-4j2j TYPO3 Security Misconfiguration in Frontend Session Handling composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high8.8 GHSA-f9hr-7cfq-mjg2 TYPO3 Arbitrary Code Execution via File List Module composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high7.5 GHSA-rxc9-f2x6-qh4w TYPO3 Security Misconfiguration for Backend User Accounts composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high7.5 GHSA-hjx5-v9xg-7h25 TYPO3 Denial of Service in Frontend Record Registration composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high7.5 GHSA-ppvg-hw62-6ph9 TYPO3 Security Misconfiguration in Install Tool Cookie composer · typo3/cms-core, composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high7.5 GHSA-96jg-pmc4-cx39 TYPO3 CMS Insecure Deserialization composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high7.5 GHSA-45wj-jv2h-jwrf TYPO3 CMS Privilege Escalation and SQL Injection composer · typo3/cms-core, composer · typo3/cms-core 2024-05-30 high7.5 GHSA-x4rj-f7m6-42c3 TYPO3 CMS Authentication Bypass vulnerability composer · typo3/cms-core, composer · typo3/cms-core, composer · typo3/cms-core 2024-05-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.