NetSight

Security Dashboard

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

Reset
294 matching advisories · page 1 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 high8.2 CVE-2026-125159 ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. 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 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 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 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 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 high7.6 CVE-2026-47346 Backend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., .FORM.YAML) to bypass the Form Framework'… composer · typo3/cms-core, composer · typo3/cms-form 2026-06-09 high7.2 CVE-2026-47343 Non-privileged backend users with file mount access were able to perform write operations (move, delete, rename) on folders representing the root of an active … composer · typo3/cms-core 2026-06-09 high7.6 CVE-2026-11607 Backend users with access to the Form Framework were able to use files not ending in .form.yaml as form definitions, which were processed without denying the i… composer · typo3/cms-core, composer · typo3/cms-form 2026-06-09 high8.2 CVE-2026-8827 The AddressRepository::getSqlQuery() method constructs a database query without properly sanitizing user input, leading to SQL Injection. composer · friendsoftypo3/tt-address 2026-05-19 high7.5 CVE-2026-6553 Changing backend users' passwords via the user settings module results in storing the cleartext password in the uc and user_settings fields of the be_users dat… composer · typo3/cms-backend 2026-04-21 high8.8 CVE-2026-1323 The mailqueue TYPO3 extension has Insecure Deserialization in `TransportFailure` class composer · cpsit/typo3-mailqueue 2026-03-17 high7.8 CVE-2026-0859 TYPO3 CMS Allows Insecure Deserialization via Mailer File Spool composer · typo3/cms-core 2026-01-13 high7.1 CVE-2025-59022 TYPO3 CMS Allows Broken Access Control in Recycler Module composer · typo3/cms-recycler 2026-01-13 high8.2 CVE-2025-12998 TYPO3 Modules Extension has Improper Authentication vulnerability composer · codingms/modules 2025-11-12 high7.1 CVE-2025-59018 TYPO3 Workspaces Module Information Disclosure composer · typo3/cms-workspaces 2025-09-09 high8.8 CVE-2025-59017 TYPO3 backend modules have Broken Access Control composer · typo3/cms-workspaces, composer · typo3/cms-recycler, composer · typo3/cms-dashboard +2 2025-09-09 high8.6 CVE-2025-9573 The ns_backup extension through 13.0.2 for TYPO3 allows command injection. ns_backup extension 2025-09-02 high8.6 CVE-2025-48207 reint_downloadmanager TYPO3 Extension is susceptible to Insecure Direct Object Reference composer · renolit/reint-downloadmanager 2025-05-21 high8.6 CVE-2025-48205 The Front End User Registration extension for TYPO3 (sr_feuser_register) allows Insecure Direct Object Reference composer · sjbr/sr-feuser-register 2025-05-21 high8.6 CVE-2025-48201 The Backup Plus extension for TYPO3 (ns_backup) has a Predictable Resource Location composer · nitsan/ns-backup 2025-05-21 high7.2 CVE-2025-47941 The TYPO3 CMS Backend has Broken Authentication in Backend MFA composer · typo3/cms-backend 2025-05-20 high7.2 CVE-2025-47940 TYPO3 Allows Privilege Escalation to System Maintainer composer · typo3/cms-core 2025-05-20 high8.0 CVE-2024-55924 TYPO3 Scheduler Module vulnerable to Cross-Site Request Forgery composer · typo3/cms-scheduler 2025-01-14 high7.5 CVE-2024-55921 TYPO3 Extension Manager Module vulnerable to Cross-Site Request Forgery composer · typo3/cms-extensionmanager 2025-01-14

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.