NetSight

Security Dashboard

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

Reset
294 matching advisories · page 3 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2024-22188 TYPO3 Install Tool vulnerable to Code Execution composer · typo3/cms-core 2024-02-13 high7.1 CVE-2024-25121 TYPO3 vulnerable to Improper Access Control Persisting File Abstraction Layer Entities via Data Handler composer · typo3/cms-core 2024-02-13 high8.8 CVE-2023-24814 TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering composer · typo3/cms-core, composer · typo3/cms 2023-02-07 high8.6 CVE-2023-25014 Broken Access Control in 3rd party TYPO3 extension "femanager" composer · in2code/femanager 2023-02-02 high8.6 CVE-2023-25013 Broken Access Control in 3rd party TYPO3 extension "femanager" composer · in2code/femanager 2023-02-02 high7.5 CVE-2022-23503 TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework composer · typo3/cms-core, composer · typo3/cms 2022-12-13 high8.8 CVE-2021-43563 An issue was discovered in the pixxio (aka pixx.io integration or DAM) extension before 1.0.6 for TYPO3. pixxio · pixx.io 2021-11-10 high8.8 CVE-2021-43562 An issue was discovered in the pixxio (aka pixx.io integration or DAM) extension before 1.0.6 for TYPO3. pixxio · pixx.io 2021-11-10 high8.8 CVE-2021-41113 Cross-Site-Request-Forgery in Backend composer · typo3/cms-core, composer · typo3/cms 2021-10-05 high7.0 CVE-2021-38623 Improper Resource Shutdown or Release in TYPO3 extension composer · webcoast/deferred-image-processing 2021-08-13 high7.5 CVE-2021-36793 CSRF token exposure in TYPO3 extension composer · lms/routes 2021-08-13 high7.2 CVE-2021-36792 The dated_news (aka Dated News) extension through 5.1.1 for TYPO3 has incorrect Access Control for confirming various applications. dated_news_project · dated_news 2021-08-13 high7.9 CVE-2021-21357 Broken Access Control in Form Framework composer · typo3/cms-form, composer · typo3/cms-core, composer · typo3/cms 2021-03-23 high8.0 CVE-2021-21355 Unrestricted File Upload in Form Framework composer · typo3/cms-form, composer · typo3/cms-core, composer · typo3/cms 2021-03-23 high8.1 CVE-2020-26228 Cleartext storage of session identifier composer · typo3/cms-core, composer · typo3/cms 2020-11-23 high8.0 CVE-2020-26216 Cross-Site Scripting through Fluid view helper arguments composer · typo3fluid/fluid 2020-11-17 high8.1 CVE-2020-15099 Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS composer · typo3/cms-core, composer · typo3/cms 2020-07-29 high8.8 CVE-2020-15098 Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS composer · typo3/cms-core, composer · typo3/cms 2020-07-29 high8.8 CVE-2020-15515 Remote code execution in turn extension for TYPO3 composer · marcwillmann/turn 2020-07-07 high8.0 CVE-2020-11069 In TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that the backend user interface and install tool are vulnerable to a same-s… composer · typo3/cms-core, composer · typo3/cms 2020-05-13 high8.8 CVE-2020-11067 In TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that backend user settings (in $BE_USER->uc) are vulnerable to insecure des… composer · typo3/cms-core, composer · typo3/cms 2020-05-13 high8.7 CVE-2020-11066 In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, calling unserialize() on malicious u… composer · typo3/cms-core, composer · typo3/cms 2020-05-13 high7.2 CVE-2019-19850 An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. composer · typo3/cms, composer · typo3/cms-core 2019-12-17 high8.8 CVE-2019-19849 An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. composer · typo3/cms-core, composer · typo3/cms 2019-12-17 high7.2 CVE-2019-19848 An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. composer · typo3/cms-core, composer · typo3/cms 2019-12-17 high7.5 CVE-2010-3668 TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows Header Injection in the secure download feature jumpurl. typo3 · typo3 2019-11-04 high8.8 CVE-2010-3663 TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 contains an insecure default value of the variable fileDenyPattern which co… composer · typo3/cms-backend 2019-11-04 high8.8 CVE-2010-3662 TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows SQL Injection on the backend. composer · typo3/cms-backend 2019-11-04 high7.3 CVE-2019-16682 The url_redirect (aka URL redirect) extension through 1.2.1 for TYPO3 fails to properly sanitize user input and is susceptible to SQL Injection. composer · sfroemken/url_redirect 2019-10-16 high8.8 CVE-2019-12747 TYPO3 8.x through 8.7.26 and 9.x through 9.5.7 allows Deserialization of Untrusted Data. composer · typo3/cms-core, composer · typo3/cms 2019-07-09

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.