NetSight

Security Dashboard

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

Reset
41 matching advisories · page 1 of 2Index updated 13 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-116274 A vulnerability has been found in JIZHICMS up to 2.5.6. n/a · JIZHICMS 26 days ago medium4.7 CVE-2026-6978 A vulnerability was detected in JiZhiCMS up to 2.5.6. JiZhiCMS 2026-04-25 critical9.8 CVE-2025-50229 Jizhicms v2.5.4 is vulnerable to SQL injection in the product editing module. jizhicms · jizhicms 2026-04-23 critical9.1 CVE-2025-50228 Jizhicms v2.5.4 is vulnerable to Server-Side Request Forgery (SSRF) in User Evaluation, Message, and Comment modules. jizhicms · jizhicms 2026-04-09 medium5.4 CVE-2026-29840 JiZhiCMS v2.5.6 and before contains a Stored Cross-Site Scripting (XSS) vulnerability in the release function within app/home/c/UserController.php. jizhicms · jizhicms 2026-03-24 medium6.3 CVE-2026-3292 A security vulnerability has been detected in jizhiCMS up to 2.5.6. jizhicms · jizhicms 2026-02-27 high7.2 CVE-2025-70397 jizhicms 2.5.6 is vulnerable to SQL Injection in Article/deleteAll and Extmolds/deleteAll via the data parameter. jizhicms · jizhicms 2026-02-17 high8.8 CVE-2020-37117 jizhiCMS 1.6.7 contains a file download vulnerability in the admin plugins update endpoint that allows authenticated administrators to download arbitrary files. jizhicms · jizhicms 2026-02-05 low2.4 CVE-2025-14013 A vulnerability was identified in JIZHICMS up to 2.5.5. jizhicms · jizhicms 2025-12-04 medium4.7 CVE-2025-14012 A vulnerability was determined in JIZHICMS up to 2.5.5. jizhicms · jizhicms 2025-12-04 medium4.7 CVE-2025-14011 A vulnerability was found in JIZHICMS up to 2.5.5. jizhicms · jizhicms 2025-12-04 medium4.3 CVE-2025-2639 A vulnerability has been found in JIZHICMS up to 1.7.0 and classified as problematic. jizhicms · jizhicms 2025-03-23 medium4.3 CVE-2025-2638 A vulnerability, which was classified as problematic, was found in JIZHICMS up to 1.7.0. jizhicms · jizhicms 2025-03-23 medium4.3 CVE-2025-2637 A vulnerability, which was classified as problematic, has been found in JIZHICMS up to 1.7.0. jizhicms · jizhicms 2025-03-23 critical9.1 CVE-2025-25785 JizhiCMS v2.5.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the component \c\PluginsController.php. jizhicms · jizhicms 2025-02-26 critical9.8 CVE-2025-25784 An arbitrary file upload vulnerability in the component \c\TemplateController.php of Jizhicms v2.5.4 allows attackers to execute arbitrary code via uploading a… jizhicms · jizhicms 2025-02-26 medium6.1 CVE-2024-34255 jizhicms v2.5.1 contains a Cross-Site Scripting(XSS) vulnerability in the message function. jizhicms · jizhicms 2024-05-08 high7.3 CVE-2024-33338 Cross Site Scripting vulnerability in jizhicms v.2.5.4 allows a remote attacker to obtain sensitive information via a crafted article publication request. jizhicms · jizhicms 2024-04-29 critical9.8 CVE-2024-32161 jizhiCMS 2.5 suffers from a File upload vulnerability. jizhicms · jizhicms 2024-04-17 critical9.8 CVE-2023-51154 Jizhicms v2.5 was discovered to contain an arbitrary file download vulnerability via the component /admin/c/PluginsController.php. jizhicms · jizhicms 2024-01-04 high8.8 CVE-2023-50692 File Upload vulnerability in JIZHICMS v.2.5, allows remote attacker to execute arbitrary code via a crafted file uploaded and downloaded to the download_url pa… jizhicms · jizhicms 2023-12-28 medium6.5 CVE-2023-43836 There is a SQL injection vulnerability in the Jizhicms 2.4.9 backend, which users can use to obtain database information jizhicms · jizhicms 2023-10-02 high7.2 CVE-2023-38948 An arbitrary file download vulnerability in the /c/PluginsController.php component of jizhi CMS 1.9.5 allows attackers to execute arbitrary code via downloadin… jizhicms · jizhicms 2023-08-03 medium6.3 CVE-2023-2927 A vulnerability was found in JIZHICMS 2.4.5. jizhicms · jizhicms 2023-05-27 medium5.4 CVE-2023-31862 jizhicms v2.4.6 is vulnerable to Cross Site Scripting (XSS). jizhicms · jizhicms 2023-05-19 high7.2 CVE-2023-27235 An arbitrary file upload vulnerability in the \admin\c\CommonController.php component of Jizhicms v2.4.5 allows attackers to execute arbitrary code via a craft… jizhicms · jizhicms 2023-03-15 medium6.5 CVE-2023-27234 A Cross-Site Request Forgery (CSRF) in /Sys/index.html of Jizhicms v2.4.5 allows attackers to arbitrarily make configuration changes within the application. jizhicms · jizhicms 2023-03-15 critical9.8 CVE-2021-36484 SQL injection vulnerability in JIZHICMS 1.9.5 allows attackers to run arbitrary SQL commands via add or edit article page. jizhicms · jizhicms 2023-02-03 high8.8 CVE-2022-45278 Jizhicms v2.3.3 was discovered to contain a SQL injection vulnerability via the /index.php/admins/Fields/get_fields.html component. jizhicms · jizhicms 2022-11-23 high8.8 CVE-2022-44140 Jizhicms v2.3.3 was discovered to contain a SQL injection vulnerability via the /Member/memberedit.html component. jizhicms · jizhicms 2022-11-23

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.