NetSight

Security Dashboard

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

Reset
88 matching advisories · page 3 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.9 CVE-2023-1758 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) in FAQ comment username parameter composer · thorsten/phpmyfaq 2023-04-05 high8.1 CVE-2023-1757 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) via FAQ News link parameter composer · thorsten/phpmyfaq 2023-04-05 high8.8 CVE-2023-1762 thorsten/phpmyfaq vulnerable privilege escalation from improper privilege management composer · thorsten/phpmyfaq 2023-03-31 high8.3 CVE-2023-0880 Misinterpretation of Input in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-17 high8.3 CVE-2023-0794 Cross-site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 high8.8 CVE-2023-0793 Weak Password Requirements in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 high8.3 CVE-2023-0791 Cross-site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 high8.8 CVE-2023-0790 Uncaught Exception in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 high8.1 CVE-2023-0787 Cross-site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 high8.4 CVE-2023-0786 Cross-site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 high7.5 CVE-2022-4409 phpMyFAQ has insecure HTTP cookies composer · thorsten/phpmyfaq 2022-12-11 high8.4 CVE-2022-3608 phpMyFAQ vulnerable to Cross-site Scripting composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2022-10-19 high7.2 CVE-2018-16651 The admin backend in phpMyFAQ before 2.9.11 allows CSV injection in reports. phpmyfaq · phpmyfaq 2018-09-07 high8.8 CVE-2018-16650 phpMyFAQ CSRF composer · thorsten/phpmyfaq 2018-09-07 high8.8 CVE-2014-6046 Multiple cross-site request forgery (CSRF) vulnerabilities in phpMyFAQ before 2.8.13 allow remote attackers to hijack the authentication of unspecified users f… phpmyfaq · phpmyfaq 2018-08-28 high7.2 CVE-2014-6045 SQL injection vulnerability in phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to execute arbitrary SQL commands via vectors … phpmyfaq · phpmyfaq 2018-08-28 high8.8 CVE-2017-15808 In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php. phpmyfaq · phpmyfaq 2017-10-23 high8.8 CVE-2017-15735 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary. phpmyfaq · phpmyfaq 2017-10-22 high8.8 CVE-2017-15734 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php. phpmyfaq · phpmyfaq 2017-10-22 high8.8 CVE-2017-15733 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/ajax.attachment.php and admin/att.main.php. phpmyfaq · phpmyfaq 2017-10-22 high8.8 CVE-2017-15732 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/news.php. phpmyfaq · phpmyfaq 2017-10-22 high8.8 CVE-2017-15731 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.adminlog.php. phpmyfaq · phpmyfaq 2017-10-22 high8.8 CVE-2017-15730 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php. phpmyfaq · phpmyfaq 2017-10-22 high8.8 CVE-2017-15729 In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for adding a glossary. phpmyfaq · phpmyfaq 2017-10-22 high7.5 CVE-2011-4825 Static code injection vulnerability in inc/function.base.php in Ajax File and Image Manager before 1.1, as used in tinymce before 1.4.2, phpMyFAQ 2.6 before 2.… phpletter · ajax_file_and_image_manager, phpmyfaq · phpmyfaq, tinymce · tinymce 2011-12-15 high7.5 CVE-2010-4558 phpMyFAQ 2.6.11 and 2.6.12, as distributed between December 4th and December 15th 2010, contains an externally introduced modification (Trojan Horse) in the ge… phpmyfaq · phpmyfaq 2010-12-17 high7.5 CVE-2006-6912 SQL injection vulnerability in phpMyFAQ 1.6.7 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors, possibly the userf… phpmyfaq · phpmyfaq 2006-12-31 high7.5 CVE-2006-6913 Unspecified vulnerability in phpMyFAQ 1.6.7 and earlier allows remote attackers to upload arbitrary PHP scripts via unspecified vectors. phpmyfaq · phpmyfaq 2006-12-31

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.