NetSight

Security Dashboard

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

Reset
807 matching advisories · page 2 of 27Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-47350 Backend users were able to move records to a different page without having edit permissions on the source page. composer · typo3/cms-core 2026-06-09 medium5.3 CVE-2026-47349 Backend users with access to the Recycler module were able to restore soft-deleted records on pages or for tables they were not authorized to modify. composer · typo3/cms-core, composer · typo3/cms-recycler 2026-06-09 medium5.1 CVE-2026-47348 Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. composer · typo3/cms-core, composer · typo3/cms-indexed-search 2026-06-09 medium5.3 CVE-2026-47347 Applications that use GeneralUtility::sanitizeLocalUrl to allow only local URLs are vulnerable to open redirect attacks if the URL is used after it has passed … composer · typo3/cms-core 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 medium5.1 CVE-2026-47345 Namespace attributes are not encoded correctly during HTML serialization. composer · typo3/html-sanitizer 2026-06-08 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 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 medium5.9 CVE-2026-46724 TYPO3 ke_search path traversal due to lack of normalization on config directory from file indexer composer · tpwd/ke_search 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 medium5.2 CVE-2026-0895 mailqueue TYPO3 extension affected by Insecure Deserialization in QueueableFileTransport composer · cpsit/typo3-mailqueue 2026-01-20 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 medium5.3 CVE-2025-59021 TYPO3 CMS Allows Broken Access Control in Redirects Module composer · typo3/cms-redirects 2026-01-13 medium5.3 CVE-2025-59020 TYPO3 CMS Allows Broken Access Control in Edit Document Controller composer · typo3/cms-backend 2026-01-13 high8.2 CVE-2025-12998 TYPO3 Modules Extension has Improper Authentication vulnerability composer · codingms/modules 2025-11-12 low2.3 CVE-2025-10316 TYPO3 "Form to Database" extension susceptible to Cross-site Scripting composer · lavitto/typo3-form-to-database 2025-09-16 medium5.3 CVE-2025-59019 TYPO3 CSV download feature information disclosure composer · typo3/cms-backend, composer · typo3/cms-recordlist 2025-09-09 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 medium5.3 CVE-2025-59016 TYPO3 CMS exposes sensitive information in an error message composer · typo3/cms-core 2025-09-09 medium6.5 CVE-2025-59015 TYPO3 CMS uses insufficient entropy when generating passwords composer · typo3/cms-core 2025-09-09 medium5.1 CVE-2025-59014 TYPO3 Bookmark Toolbar vulnerable to denial of service composer · typo3/cms-backend 2025-09-09 medium5.3 CVE-2025-59013 TYPO3 CMS has an open‑redirect vulnerability composer · typo3/cms-core 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 medium5.3 CVE-2025-7900 Femanager extension for TYPO3 allows Insecure Direct Object Reference composer · in2code/femanager 2025-07-22 medium6.0 CVE-2025-7899 Powermail extension for TYPO3 allows Insecure Direct Object Reference composer · in2code/powermail 2025-07-22

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.