NetSight

Security Dashboard

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

Reset
148 matching advisories · page 4 of 5Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2023-5317 phpMyFaq Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-09-30 medium5.2 CVE-2023-3469 phpMyFAQ Cross-site Scripting composer · thorsten/phpmyfaq 2023-06-30 medium6.7 CVE-2023-2999 thorsten/phpmyfaq vulnerable to cross-site scripting composer · thorsten/phpmyfaq 2023-05-31 medium6.0 CVE-2023-2998 thorsten/phpmyfaq vulnerable to cross-site scripting composer · thorsten/phpmyfaq 2023-05-31 medium5.4 CVE-2023-2753 phpMyFAQ vulnerable to stored Cross-site Scripting composer · thorsten/phpmyfaq 2023-05-17 medium5.4 CVE-2023-2752 phpMyFAQ vulnerable to stored Cross-site Scripting composer · thorsten/phpmyfaq 2023-05-17 medium6.1 CVE-2023-2427 Cross Site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-05-05 medium6.1 CVE-2023-2428 phpMyFAQ vulnerable to Stored Cross-site Scripting composer · thorsten/phpmyfaq 2023-04-30 medium5.4 CVE-2023-1875 Cross-site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-04-22 medium6.3 CVE-2023-1885 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) via category field name parameter composer · thorsten/phpmyfaq 2023-04-05 medium4.7 CVE-2023-1884 thorsten/phpmyfaq vulnerable to cross-site scripting (XSS) via stopword parameter composer · thorsten/phpmyfaq 2023-04-05 medium5.4 CVE-2023-1883 thorsten/phpmyfaq vulnerable to improper access control composer · thorsten/phpmyfaq 2023-04-05 medium4.7 CVE-2023-1879 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) via updatecategory parameter composer · thorsten/phpmyfaq 2023-04-05 medium4.7 CVE-2023-1756 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) via HTML export composer · thorsten/phpmyfaq 2023-04-05 medium5.4 CVE-2023-1761 phpMyFAQ Code Injection vulnerability composer · thorsten/phpmyfaq 2023-03-31 medium4.8 CVE-2023-1760 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-03-31 medium4.8 CVE-2023-1759 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-03-31 medium5.4 CVE-2023-1755 phpMyFAQ Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-03-31 medium4.7 CVE-2023-1754 phpMyFAQ vulnerable to improper input validation composer · thorsten/phpmyfaq 2023-03-31 medium5.5 CVE-2023-1753 phpMyFAQ has weak password requirements composer · thorsten/phpmyfaq 2023-03-31 medium5.4 CVE-2023-0792 Code Injection in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-02-12 medium6.1 CVE-2023-0314 phpMyFAQ Reflected Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-01-15 medium5.4 CVE-2023-0313 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-01-15 medium6.1 CVE-2023-0312 thorsten/phpmyfaq is vulnerable to cross-site scripting (XSS) composer · thorsten/phpmyfaq 2023-01-15 medium5.4 CVE-2023-0310 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-01-15 medium5.4 CVE-2023-0309 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-01-15 medium5.4 CVE-2023-0308 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-01-15 medium5.4 CVE-2023-0306 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-01-15 medium5.4 CVE-2022-4408 phpMyFAQ vulnerable to Cross-site Scripting composer · thorsten/phpmyfaq 2022-12-11 medium6.1 CVE-2022-4407 phpMyFAQ vulnerable to Cross-site Scripting composer · thorsten/phpmyfaq 2022-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.