NetSight

Security Dashboard

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

Reset
148 matching advisories · page 3 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-57994 phpMyFAQ before 4.1.5 applies inconsistent active=yes and publication-date filtering across its public FAQ API endpoints, allowing unauthenticated attackers to… phpMyFAQ 2026-07-10 medium6.5 CVE-2026-49205 phpMyFAQ: Missing userHasPermission() in 4 API write endpoints (CVE-2026-24421 Incomplete Fix) composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-06-18 medium5.3 CVE-2026-46365 phpMyFAQ before 4.1.2 contains a missing authorization vulnerability in the DELETE /admin/api/content/tags/{tagId} endpoint that allows any authenticated user … composer · phpMyFAQ/phpMyFAQ, composer · thorsten/phpMyFAQ 2026-05-15 medium4.3 CVE-2026-45009 phpMyFAQ before 4.1.2 contains an insufficient authorization vulnerability in admin-api routes that allows authenticated ordinary users to access administrativ… composer · phpMyFAQ/phpMyFAQ, composer · thorsten/phpMyFAQ, composer · thorsten/phpmyfaq +1 2026-05-06 medium5.3 CVE-2026-45007 Duplicate Advisory: phpMyFAQ's Missing CONFIGURATION_EDIT Permission Check on 12 Admin API Configuration Tab Endpoints Allows Information Disclosure by Any Authenticated User composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-05-06 medium5.1 CVE-2026-46360 phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in SvgSanitizer::decodeAllEntities() that limits recursive entity decoding to 5 iter… composer · phpMyFAQ/phpMyFAQ, composer · thorsten/phpMyFAQ, composer · phpmyfaq/phpmyfaq +1 2026-05-06 medium5.1 CVE-2026-46363 phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in FAQ creation and update endpoints that bypass sanitization through encode-decode … composer · phpMyFAQ/phpMyFAQ, composer · thorsten/phpMyFAQ, composer · phpmyfaq/phpmyfaq +1 2026-05-06 medium5.4 GHSA-7cx3-2qx2-3g6w phpMyFAQ's Missing Authorization on Tag Deletion Allows Any Authenticated User to Delete Tags composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 2026-05-06 medium5.4 CVE-2026-34974 phpMyFAQ: SVG Sanitizer Bypass via HTML Entity Encoding Leads to Stored XSS and Privilege Escalation composer · thorsten/phpmyfaq 2026-04-01 medium5.3 CVE-2026-34973 phpMyFAQ has a LIKE Wildcard Injection in Search.php — Unescaped % and _ Metacharacters Enable Broad Content Disclosure composer · thorsten/phpmyfaq 2026-04-01 medium6.1 CVE-2026-34729 phpMyFAQ: Stored XSS via Regex Bypass in Filter::removeAttributes() composer · phpmyfaq/phpmyfaq 2026-04-01 medium6.1 CVE-2026-32629 phpMyFAQ is Vulnerable to Stored XSS via Unsanitized Email Field in Admin FAQ Editor composer · thorsten/phpmyfaq, composer · phpmyfaq/phpmyfaq 2026-03-31 medium5.3 CVE-2026-24422 phpMyFAQ: Public API endpoints expose emails and invisible questions composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 2026-01-23 medium6.5 CVE-2026-24421 phpMyFAQ: /api/setup/backup accessible to any authenticated user (authz missing) composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 2026-01-23 medium6.5 CVE-2026-24420 phpMyFAQ: Attachment download allowed without dlattachment right (broken access control) composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 2026-01-23 medium5.4 CVE-2025-68951 phpMyFAQ has Stored XSS in user list via admin-managed display_name composer · thorsten/phpmyfaq 2025-12-29 medium5.2 CVE-2024-56199 phpMyFAQ Vulnerable to Stored HTML Injection at FAQ composer · phpmyfaq/phpmyfaq, composer · thorsten/phpmyfaq 2025-01-02 medium4.9 CVE-2024-55889 thorsten/phpmyfaq Unintended File Download Triggered by Embedded Frames composer · thorsten/phpmyfaq 2024-12-13 medium4.3 CVE-2024-29179 phpMyFAQ Stored Cross-site Scripting at File Attachments composer · phpmyfaq/phpmyfaq 2024-03-25 medium5.1 CVE-2024-28108 phpMyFAQ Stored HTML Injection at contentLink composer · phpmyfaq/phpmyfaq 2024-03-25 medium4.3 CVE-2024-28106 phpMyFAQ Stored Cross-site Scripting at FAQ News Content composer · phpmyfaq/phpmyfaq 2024-03-25 medium5.5 CVE-2024-27300 phpMyFAQ stored Cross-site Scripting at user email composer · phpmyfaq/phpmyfaq 2024-03-25 medium6.5 CVE-2024-24574 phpMyFAQ vulnerable to stored XSS on attachments filename composer · phpmyfaq/phpmyfaq 2024-02-05 medium6.5 CVE-2024-22208 phpMyFAQ sharing FAQ functionality can easily be abused for phishing purposes composer · phpmyfaq/phpmyfaq 2024-02-05 medium5.7 CVE-2024-22202 phpMyFAQ User Removal Page Allows Spoofing Of User Details composer · phpmyfaq/phpmyfaq 2024-02-05 medium5.4 CVE-2023-6890 phpMyFAQ Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-12-16 medium5.4 CVE-2023-6889 phpMyFAQ Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-12-16 medium5.4 CVE-2023-5867 Cross-site Scripting (XSS) in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-10-31 medium6.3 CVE-2023-5866 Sensitive cookie in HTTPS session without 'Secure' attribute in thorsten/phpmyfaq composer · thorsten/phpmyfaq 2023-10-31 medium6.1 CVE-2023-5863 phpMyFAQ Cross-site Scripting vulnerability composer · thorsten/phpmyfaq 2023-10-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.