NetSight

Security Dashboard

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

Reset
88 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2026-56396 phpMyFAQ before 4.1.4 contains missing authorization vulnerabilities in editUser() and updateUserRights() endpoints that allow authenticated administrators to … thorsten · phpMyFAQ 2026-06-21 high8.8 CVE-2026-35675 phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in the password reset endpoint that allows unauthenticated attackers to reset any user ac… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-20 high8.7 CVE-2026-35672 phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in API v4.0 where the default empty api.apiClientToken allows unauthenticated users to cr… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-20 high8.7 CVE-2026-35671 phpMyFAQ before 4.1.3 contains an insecure direct object reference vulnerability in the admin API user password endpoint that allows authenticated administrato… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-20 high8.8 CVE-2026-35676 phpMyFAQ before 4.1.3 contains an unauthenticated password reset vulnerability in the user password update API endpoint that allows attackers to change account… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-20 high7.0 CVE-2026-45008 phpMyFAQ before 4.1.2 contains a path traversal vulnerability in Client::deleteClientFolder that allows admins with INSTANCE_DELETE permission to delete arbitr… composer · phpMyFAQ/phpMyFAQ, composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 high7.5 CVE-2026-46366 phpMyFAQ before 4.1.2 contains an information disclosure vulnerability in the getIdFromSolutionId() method that lacks permission filtering, allowing unauthenti… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 high7.7 CVE-2026-46359 phpMyFAQ before 4.1.2 contains a sql injection vulnerability in CurrentUser::setTokenData that allows authenticated attackers to execute arbitrary SQL by injec… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 high8.2 CVE-2026-46361 phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in search.twig where result.question and result.answerPreview are rendered with the … composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 high7.1 CVE-2026-46362 phpMyFAQ before 4.1.2 contains an authorization bypass vulnerability in AbstractAdministrationController::userHasPermission() that fails to terminate execution… composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 high8.3 CVE-2026-46367 phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in Utils::parseUrl() that allows authenticated users to inject JavaScript via malfor… composer · phpMyFAQ/phpMyFAQ, composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 high8.7 CVE-2026-34728 phpMyFAQ: Path Traversal - Arbitrary File Deletion in MediaBrowserController composer · phpmyfaq/phpmyfaq 2026-04-01 high7.5 CVE-2026-27836 phpMyFAQ Allows Unauthenticated Account Creation via WebAuthn Prepare Endpoint composer · thorsten/phpmyfaq 2026-02-27 high7.5 CVE-2025-69200 phpMyFAQ has unauthenticated config backup download via /api/setup/backup composer · thorsten/phpmyfaq 2025-12-29 high8.8 CVE-2023-53929 phpMyFAQ contains a CSV injection vulnerability composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2025-12-17 high7.2 CVE-2025-62519 phpMyFAQ has Authenticated SQL Injection in Configuration Update Functionality composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2025-11-17 high8.1 CVE-2025-59943 phpMyFAQ duplicate email registration allows multiple accounts with the same email composer · thorsten/phpmyfaq 2025-10-03 high8.6 CVE-2024-54141 phpMyFAQ Generates an Error Message Containing Sensitive Information if database server is not available composer · thorsten/phpmyfaq 2024-12-06 high8.8 CVE-2024-28107 phpMyFAQ SQL injections at insertentry & saveentry composer · phpmyfaq/phpmyfaq 2024-03-25 high7.2 CVE-2024-28105 phpMyFAQ's File Upload Bypass at Category Image Leads to RCE composer · phpmyfaq/phpmyfaq 2024-03-25 high8.8 CVE-2024-27299 phpMyFAQ SQL Injection at "Save News" composer · phpmyfaq/phpmyfaq 2024-03-25 high7.4 CVE-2023-5864 phpMyFAQ Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-10-31 high8.3 CVE-2023-5319 phpMyFAQ Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-09-30 high8.8 CVE-2023-4007 phpMyFAQ Stored Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-07-31 high8.2 CVE-2023-2550 Cross Site Scripting in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-05-05 high8.3 CVE-2023-1887 thorsten/phpmyfaq vulnerable to business logic errors composer · thorsten/phpmyfaq 2023-04-05 high7.3 CVE-2023-1886 thorsten/phpmyfaq vulnerable to authentication bypass composer · thorsten/phpmyfaq 2023-04-05 high8.1 CVE-2023-1882 thorsten/phpmyfaq vulnerable to DOM cross-site scripting (XSS) via configuration privacy note URL parameter composer · thorsten/phpmyfaq 2023-04-05 high8.3 CVE-2023-1880 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) via artlang parameter composer · thorsten/phpmyfaq 2023-04-05 high8.3 CVE-2023-1878 thorsten/phpmyfaq vulnerable to stored cross-site scripting (XSS) via adminlog composer · thorsten/phpmyfaq 2023-04-05

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.