NetSight

Security Dashboard

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

Reset
807 matching advisories · page 1 of 27Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-125165 The RSS widget of the dashboard allows backend users to configure the URL of the RSS feed in the widget settings. TYPO3 · TYPO3 CMS 4 days ago medium6.3 CVE-2026-125164 The file dump controller (eID=dumpFile) delivers files, file references and processed files identified by their uid, protected by a token. TYPO3 · TYPO3 CMS 4 days ago medium6.3 CVE-2026-125163 The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload. TYPO3 · TYPO3 CMS 4 days ago high8.2 CVE-2026-125162 The cHash argument, which ensures that only URL arguments originally generated by TYPO3 create separate page cache entries, was treated inconsistently when it … TYPO3 · TYPO3 CMS 4 days ago medium5.3 CVE-2026-125161 The fix for TYPO3-CORE-SA-2026-009 was incomplete. TYPO3 · TYPO3 CMS 4 days ago medium6.3 CVE-2026-125160 Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. TYPO3 · TYPO3 CMS 4 days ago high8.2 CVE-2026-125159 ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. TYPO3 · TYPO3 CMS 4 days ago critical9.4 CVE-2026-119623 The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the p… TYPO3 · TYPO3 CMS 4 days ago high7.1 CVE-2026-119622 The backend endpoint for adding online media (e.g. TYPO3 · TYPO3 CMS 4 days ago high7.7 CVE-2026-119621 When importing a T3D or XML file in the Import/Export module, the file hash values of imported files were taken from the import data without validation and use… TYPO3 · TYPO3 CMS 4 days ago medium6.9 CVE-2026-120328 The click tracking middleware does not validate the authentication code of a recipient if the code is omitted. TYPO3 · Extension "Mail" 18 days ago medium5.3 CVE-2026-120327 The click tracking middleware accepts an arbitrary target URL and redirects to it. Attackers can... TYPO3 · Extension "Mail" 18 days ago medium5.3 CVE-2026-120329 Saving the configuration of the mail backend module writes submitted settings to the page TSconfig without restricting them to the configuration options of the… TYPO3 · Extension "Mail" 18 days ago medium5.3 CVE-2026-120331 Content of external URL mails, their stylesheets and images to embed is fetched by the server without validating the target host. TYPO3 · Extension "Mail" 18 days ago high7.1 CVE-2026-120330 Backend actions and ajax routes of the mail module do not check whether the backend user has access to the page of the requested mail or recipient group. TYPO3 · Extension "Mail" 18 days ago medium5.1 CVE-2026-120332 The HTML content of mails and tracked URLs are rendered unescaped in the backend module. Backend... TYPO3 · Extension "Mail" 18 days ago high8.8 CVE-2026-120333 The actions linked in the emails of the extension (e.g. to confirm a registration or the deletion... TYPO3 · Extension "Frontend User Registration" 18 days ago high7.1 CVE-2026-113459 In versions running on TYPO3 10 and 11, the configured OpenAI API key is embedded in every backend page, so that the editor plugin can contact the OpenAI servi… 32 days ago medium5.4 CVE-2023-50460 An issue was discovered in the femanager extension 7.x before 7.2.3 for TYPO3. femanager extension 2026-09-14 medium5.3 CVE-2026-77131 When OpenSSL is unavailable on the server, the extension transmits TYPO3 system information in cleartext instead of encrypting it. 2026-08-25 high7.3 GHSA-4f2f-jr2m-j7p4 Duplicate Advisory: TYPO3-CORE-SA-2026-021: Broken Access Control in Backend and Install Tool composer · typo3/cms-core, composer · typo3/cms-core 2026-08-11 high7.3 CVE-2026-19418 The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 (CVE-2020-11069) became ineffective in TYPO3 v13.0, where TYPO3 CMS started serving the backend… composer · typo3/cms-backend, composer · typo3/cms-core 2026-08-11 medium6.3 GHSA-p8pr-442q-qf8g Duplicate Advisory: TYPO3-CORE-SA-2026-020: TYPO3 CMS - Unrestricted File Upload in Form Framework composer · typo3/cms-form 2026-07-14 medium6.3 CVE-2026-15305 Users were able to upload files with arbitrary MIME types to forms using FileUpload or ImageUpload elements with allowedMimeTypes configured. composer · typo3/cms-form 2026-07-14 high7.1 CVE-2026-49742 Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. composer · typo3/cms-core, composer · typo3/cms-filelist 2026-06-09 high8.7 CVE-2026-49741 Backend users with write access to the form_definition database table were able to directly create, update, or delete form definition records via DataHandler, … composer · typo3/cms-core, composer · typo3/cms-form 2026-06-09 medium6.3 CVE-2026-49740 TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restriction… composer · typo3/cms-core 2026-06-09 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 medium5.3 CVE-2026-47352 Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outsi… composer · typo3/cms-core, composer · typo3/cms-backend 2026-06-09 medium5.3 CVE-2026-47351 Backend users were able to insert arbitrary records and files into the TYPO3 clipboard without proper read permission checks, which allowed users to gather inf… composer · typo3/cms-core, composer · typo3/cms-backend 2026-06-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.