NetSight

Security Dashboard

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

Reset
58 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-119426 phpMyAdmin through 5.2.3 contains a cross-site request forgery vulnerability that allows remote attackers to execute arbitrary SQL by bypassing CSRF token chec… phpmyadmin · phpmyadmin 22 days ago high7.7 CVE-2026-37149 GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0 was discovered to contain a SQL injection vulnerability in the scost parameter in /grocery/… 2026-06-25 high8.8 CVE-2020-37116 GUnet OpenEclass 1.7.3 includes phpMyAdmin 2.10.0.2 by default, which allows remote logins. gunet · open_eclass_platform 2026-02-03 high7.5 CVE-2022-0813 Exposure of Sensitive Information to an Unauthorized Actor in PhpMyAdmin composer · phpmyadmin/phpmyadmin 2022-03-10 high7.5 CVE-2021-26939 An information disclosure issue exists in henriquedornas 5.2.17 because an attacker can dump phpMyAdmin SQL content. henriquedornas · henriquedornas 2021-02-10 high8.8 CVE-2020-22278 phpMyAdmin through 5.0.2 allows CSV injection via Export Section. phpmyadmin · phpmyadmin 2020-11-04 high8.0 CVE-2020-10802 phpMyAdmin SQL injection vulnerability composer · phpmyadmin/phpmyadmin 2020-03-22 high8.0 CVE-2020-10804 phpMyAdmin SQL Injection composer · phpmyadmin/phpmyadmin 2020-03-22 high8.8 CVE-2020-5504 phpMyAdmin SQL injection in user accounts page composer · phpmyadmin/phpmyadmin 2020-01-09 high8.8 CVE-2018-19969 phpMyAdmin CSRF Vulnerability composer · phpmyadmin/phpmyadmin 2018-12-11 high8.8 CVE-2018-12613 phpMyAdmin Improper Authentication composer · phpmyadmin/phpmyadmin 2018-06-21 high8.8 CVE-2018-10188 phpMyAdmin CSRF vulnerability allowing arbitrary SQL execution composer · phpmyadmin/phpmyadmin 2018-04-19 high8.8 CVE-2017-1000499 phpMyAdmin CSRF Vulnerability composer · phpmyadmin/phpmyadmin 2018-01-03 high7.5 CVE-2017-1000018 phpMyAdmin DoS Vulnerability composer · phpmyadmin/phpmyadmin 2017-07-17 high8.8 CVE-2017-1000017 phpMyAdmin SSRF in replication composer · phpmyadmin/phpmyadmin 2017-07-17 high7.5 CVE-2017-1000016 phpMyAdmin Cookie attribute injection attack composer · phpmyadmin/phpmyadmin 2017-07-17 high7.5 CVE-2017-1000014 phpMyAdmin DoS Vulnerability composer · phpmyadmin/phpmyadmin 2017-07-17 high8.6 CVE-2016-6621 phpMyAdmin server-side request forgery (SSRF) composer · phpmyadmin/phpmyadmin 2017-01-31 high7.5 CVE-2016-9864 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high7.5 CVE-2016-9863 phpMyAdmin DoS Vulnerability composer · phpmyadmin/phpmyadmin 2016-12-11 high7.5 CVE-2016-9862 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high7.5 CVE-2016-9861 phpMyAdmin Bypass white-list protection for URL redirection composer · phpmyadmin/phpmyadmin 2016-12-11 high8.1 CVE-2016-6633 phpMyAdmin Remote code execution vulnerability when PHP is running with dbase extension composer · phpmyadmin/phpmyadmin 2016-12-11 high7.5 CVE-2016-6631 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high8.8 CVE-2016-6619 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high8.1 CVE-2016-6617 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high7.5 CVE-2016-6616 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high8.1 CVE-2016-6611 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 high8.8 CVE-2016-6609 phpMyAdmin PHP code injection composer · phpmyadmin/phpmyadmin 2016-12-11 high8.1 CVE-2016-6606 An issue was discovered in cookie encryption in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11

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.