NetSight

Security Dashboard

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

Reset
37 matching advisories · page 1 of 2Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.1 CVE-2026-49738 The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, cau… composer · typo3/cms-core 2026-06-09 low2.1 CVE-2026-47344 When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as val… composer · typo3/html-sanitizer 2026-06-08 low2.3 CVE-2025-10316 TYPO3 "Form to Database" extension susceptible to Cross-site Scripting composer · lavitto/typo3-form-to-database 2025-09-16 low3.8 CVE-2025-47938 TYPO3 Unverified Password Change for Backend Users composer · typo3/cms-core, composer · typo3/cms-setup 2025-05-20 low3.7 CVE-2025-47937 TYPO3 Allows Information Disclosure via DBAL Restriction Handling composer · typo3/cms-core 2025-05-20 low3.3 CVE-2025-47936 TYPO3 CMS Webhooks Server Side Request Forgery composer · typo3/cms-webhooks 2025-05-20 low3.1 CVE-2024-55891 TYPO3 Information Disclosure via Exception Handling/Logger composer · typo3/cms-install 2025-01-14 low3.1 CVE-2024-47780 Information Disclosure in TYPO3 Page Tree composer · typo3/cms-backend 2024-10-08 low GHSA-h934-f4m4-wc8x Typo3 Information Disclosure in Page Tree composer · typo3/cms 2024-06-05 low3.7 GHSA-c7p6-3c9c-f88q Information Disclosure in TYPO3 CMS composer · typo3/cms, composer · typo3/cms 2024-06-05 low3.5 CVE-2024-34355 TYPO3 vulnerable to an HTML Injection in the History Module composer · typo3/cms-core 2024-05-14 low3.7 CVE-2023-47126 Information Disclosure in typo3/cms-install tool composer · typo3/cms-install 2023-11-14 low3.7 CVE-2023-38499 Information Disclosure due to Out-of-scope Site Resolution composer · typo3/cms-core 2023-07-25 low3.5 CVE-2016-15032 ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as problematic has been found in mback2k mh_httpbl Extension up to 1.1.7 on TYPO3. mh_httpbl_project · mh_httpbl 2023-06-02 low3.7 CVE-2020-26229 XML External Entity in Dashboard Widget composer · typo3/cms-core, composer · typo3/cms 2020-11-23 low3.7 CVE-2020-11063 In TYPO3 CMS versions 10.4.0 and 10.4.1, it has been discovered that time-based attacks can be used with the password reset functionality for backend users. composer · typo3/cms-core, composer · typo3/cms 2020-05-13 low3.5 CVE-2015-5956 The sanitizeLocalUrl function in TYPO3 6.x before 6.2.15, 7.x before 7.4.0, 4.5.40, and earlier allows remote authenticated users to bypass the XSS filter and … composer · typo3/cms 2015-09-16 low3.5 CVE-2015-4608 Cross-site scripting (XSS) vulnerability in the BE User Log (beko_beuserlog) extension 1.1.1 and earlier for TYPO3 allows remote authenticated users to inject … be_user_log_project · be_user_log 2015-06-16 low2.6 CVE-2015-2047 The rsaauth extension in TYPO3 4.3.0 through 4.3.14, 4.4.0 through 4.4.15, 4.5.0 through 4.5.39, and 4.6.0 through 4.6.18, when configured for the frontend, al… typo3 · typo3, debian · debian_linux 2015-02-23 low3.5 CVE-2014-6237 Cross-site scripting (XSS) vulnerability in the News Pack extension 0.1.0 and earlier for TYPO3 allows remote authenticated users to inject arbitrary web scrip… news_pack_project · news_pack 2014-09-11 low3.5 CVE-2014-3949 Cross-site scripting (XSS) vulnerability in the layout wizard in the Grid Elements (gridelements) extension before 1.5.1 and 2.0.x before 2.0.3 for TYPO3 allow… jo_hasenau · gridelements 2014-06-04 low3.5 CVE-2014-3943 Multiple cross-site scripting (XSS) vulnerabilities in unspecified backend components in TYPO3 4.5.0 before 4.5.34, 4.7.0 before 4.7.19, 6.0.0 before 6.0.14, 6… composer · typo3/cms 2014-06-03 low2.6 CVE-2013-7078 Cross-site scripting (XSS) vulnerability in the errorAction method in the ActionController base class in the Extbase Framework in TYPO3 4.5.0 through 4.5.31, 4… composer · typo3/cms-core 2014-01-19 low3.5 CVE-2013-7074 Multiple cross-site scripting (XSS) vulnerabilities in Content Editing Wizards in TYPO3 4.5.x before 4.5.32, 4.7.x before 4.7.17, 6.0.x before 6.0.12, 6.1.x be… composer · typo3/cms 2013-12-21 low3.5 CVE-2012-6148 Cross-site scripting (XSS) vulnerability in the function menu API in TYPO3 4.5.x before 4.5.21, 4.6.x before 4.6.14, and 4.7.x before 4.7.6 allows remote authe… composer · typo3/cms 2013-07-01 low3.5 CVE-2012-6147 Cross-site scripting (XSS) vulnerability in the tree render API (TCA-Tree) in the Backend API in TYPO3 4.5.x before 4.5.21, 4.6.x before 4.6.14, and 4.7.x befo… composer · typo3/cms 2013-07-01 low3.5 CVE-2012-6145 Cross-site scripting (XSS) vulnerability in the Backend History module in TYPO3 4.5.x before 4.5.21, 4.6.x before 4.6.14, and 4.7.x before 4.7.6 allows remote … composer · typo3/cms 2013-07-01 low3.5 CVE-2012-3529 The configuration module in the backend in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to o… composer · typo3/cms 2012-09-05 low3.5 CVE-2012-3528 Multiple cross-site scripting (XSS) vulnerabilities in the backend in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allow remote authen… composer · typo3/cms 2012-09-05 low3.5 CVE-2012-1606 Multiple cross-site scripting (XSS) vulnerabilities in the Backend component in TYPO3 4.4.0 through 4.4.13, 4.5.0 through 4.5.13, 4.6.0 through 4.6.6, 4.7, and… composer · typo3/cms 2012-09-04

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.