NetSight

Security Dashboard

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

Reset
261 matching advisories · page 3 of 9Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2026-109573 phpMyFAQ before 4.1.9 contains an SQL injection vulnerability in PdoMysql::escape(), which escapes single quotes with backslashes that are treated literally wh… phpMyFAQ 40 days ago low3.3 CVE-2026-108851 phpMyFAQ through 4.1.10 contains a missing authorization vulnerability in the MCP server faq_search tool that allows MCP clients to read restricted FAQs becaus… phpMyFAQ 41 days ago high8.5 CVE-2026-56738 phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 58 days ago high8.1 CVE-2026-56737 phpMyFAQ's two-factor authentication login bypasses the password factor composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 58 days ago high8.2 CVE-2026-56736 phpMyFAQ has Stored XSS in Admin FAQ Editor via HTML Entity Bypass in Frontend FAQ Submission composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 58 days ago medium5.4 CVE-2026-85593 phpMyFAQ versions before 4.1.8 contain a stored cross-site scripting vulnerability in FaqHelper::convertOldInternalLinks() that calls html_entity_decode() on s… phpMyFAQ 2026-09-04 low3.7 CVE-2026-85592 phpMyFAQ before 4.1.8 contains an authorization bypass vulnerability in the question creation endpoint where the isAddingQuestionsAllowed() method grants acces… phpMyFAQ 2026-09-04 high7.1 CVE-2026-85591 phpMyFAQ versions before 4.1.8 contain an authentication bypass vulnerability in the user control panel API endpoint that allows authenticated attackers to cha… phpMyFAQ 2026-09-04 high7.1 CVE-2026-85590 phpMyFAQ before 4.1.8 contains an authentication bypass vulnerability in its two-factor authentication (TOTP) disable functionality. phpMyFAQ 2026-09-04 medium5.3 CVE-2026-85589 phpMyFAQ before 4.2.0-alpha.2 contains a missing authorization vulnerability in the admin dashboard API endpoints searches and content-health that enforce only… phpMyFAQ 2026-09-04 medium5.3 CVE-2026-85588 phpMyFAQ versions before 4.1.8 include live TOTP shared secrets in plaintext within user data export ZIP files. phpMyFAQ 2026-09-04 medium5.3 CVE-2026-85587 phpMyFAQ before 4.1.8 enforces incorrect permission checks on admin content pages, allowing lesser-privileged editors to read draft and inactive content. phpMyFAQ 2026-09-04 medium6.9 CVE-2026-85586 phpMyFAQ versions before 4.1.8 fail to validate CAPTCHA when the store parameter is set to 'now' in question submission requests. phpMyFAQ 2026-09-04 high8.8 GHSA-pg62-f8g4-4wqh phpMyFAQ privilege escalation: GroupController::updatePermissions lets a GROUP_EDIT admin grant rights they do not hold composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 2026-08-25 medium5.3 GHSA-mf8r-wm2w-f8c5 phpMyFAQ public FAQ APIs expose inactive FAQ content composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-08-25 medium4.9 GHSA-88g4-74f3-63x9 phpMyFAQ has Potential Authenticated Path Traversal in PDF Export composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-08-25 medium5.3 CVE-2026-76215 phpMyFAQ before 4.1.7 fails to apply parent FAQ visibility checks before returning child resources including comments and attachments. phpmyfaq · phpmyfaq 2026-08-19 high7.4 CVE-2026-76214 phpMyFAQ before 4.1.7 fails to persist the WebAuthn login challenge generated by prepareForLogin, because neither WebAuthn controller saves the mutated key obj… phpmyfaq · phpmyfaq 2026-08-19 high7.4 CVE-2026-76213 phpMyFAQ before 4.1.7 contains a brute-force vulnerability in the two-factor authentication step where the failure counter is session-scoped and reset on each … phpmyfaq · phpmyfaq 2026-08-19 medium5.3 CVE-2026-76212 phpMyFAQ before 4.1.7, when configured to use PostgreSQL via the native pgsql PHP extension, declares an incorrect LIKE ESCAPE character ('=') in the Search/Da… phpmyfaq · phpmyfaq 2026-08-19 medium4.3 CVE-2026-76211 phpMyFAQ before 4.1.7 fails to properly enforce CONFIGURATION_EDIT permission on admin API read endpoints for LDAP, Elasticsearch, OpenSearch, and dashboard co… phpmyfaq · phpmyfaq 2026-08-19 medium6.5 CVE-2026-76210 phpMyFAQ before 4.1.6 does not adequately sanitize HTML in FAQ answers before generating PDFs via TCPDF. phpmyfaq · phpmyfaq 2026-08-19 medium4.3 CVE-2026-76209 phpMyFAQ versions before v4.1.6 fail to validate the security.enableRegistration setting in API endpoints, allowing attackers to create user accounts when regi… phpmyfaq · phpmyfaq 2026-08-19 high8.1 CVE-2026-76207 phpMyFAQ before 4.1.7 contains a two-factor authentication bypass vulnerability where remember-me tokens are issued before 2FA verification completes. phpmyfaq · phpmyfaq 2026-08-19 medium5.3 CVE-2026-76206 phpMyFAQ versions before 4.1.7 fail to validate active status in the PDF export endpoint, allowing unauthenticated attackers to retrieve draft FAQ metadata. phpmyfaq · phpmyfaq 2026-08-19 high8.1 CVE-2026-76205 phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embeddin… phpmyfaq · phpmyfaq 2026-08-19 medium5.3 CVE-2026-75920 phpMyFAQ before v4.1.6 writes content backup ZIP archives to the web-accessible document root at content.zip, exposing sensitive files including database crede… phpmyfaq · phpmyfaq 2026-08-19 medium5.3 CVE-2026-75919 phpMyFAQ before 4.1.7 contains an authentication bypass vulnerability in SetupController that allows unauthenticated attackers to run database migrations and c… phpmyfaq · phpmyfaq 2026-08-19 high8.8 CVE-2026-75918 phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. phpmyfaq · phpmyfaq 2026-08-19 high8.8 CVE-2026-76208 phpMyFAQ versions 3.1.0 before 4.1.7 contain an authentication bypass vulnerability in AuthLdap::create(). phpmyfaq · phpmyfaq, thorsten · phpMyFAQ 2026-08-19

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.