NetSight

Security Dashboard

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

Reset
35 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.7 CVE-2025-14837 A vulnerability has been found in ZZCMS 2025. zzcms · zzcms 2025-12-18 medium6.3 CVE-2025-13171 A vulnerability was identified in ZZCMS 2023. zzcms · zzcms 2025-11-14 medium4.3 CVE-2025-1949 A vulnerability, which was classified as problematic, has been found in ZZCMS 2025. zzcms · zzcms 2025-03-04 medium4.7 CVE-2024-11242 A vulnerability was found in ZZCMS 2023. zzcms · zzcms 2024-11-15 medium6.3 CVE-2024-10293 A vulnerability was found in ZZCMS 2023. zzcms · zzcms 2024-10-23 medium6.3 CVE-2024-10292 A vulnerability was found in ZZCMS 2023 and classified as critical. zzcms · zzcms 2024-10-23 medium6.3 CVE-2024-10291 A vulnerability has been found in ZZCMS 2023 and classified as critical. zzcms · zzcms 2024-10-23 medium5.3 CVE-2024-10290 A vulnerability, which was classified as problematic, was found in ZZCMS 2023. zzcms · zzcms 2024-10-23 medium5.3 CVE-2024-44821 ZZCMS 2023 contains a vulnerability in the captcha reuse logic located in /inc/function.php. zzcms · zzcms 2024-09-04 medium5.4 CVE-2024-44818 Cross Site Scripting vulnerability in ZZCMS v.2023 and before allows a remote attacker to obtain sensitive information via the HTTP_Referer header of the caina… zzcms · zzcms 2024-09-04 medium6.1 CVE-2024-44820 A sensitive information disclosure vulnerability exists in ZZCMS v.2023 and before within the eginfo.php file located at /3/E_bak5.1/upload/. zzcms · zzcms 2024-09-04 medium6.1 CVE-2024-44819 Cross Site Scripting vulnerability in ZZCMS v.2023 and before allows a remote attacker to obtain sensitive information via a crafted script to the pagename par… zzcms · zzcms 2024-09-04 medium4.3 CVE-2024-7925 A vulnerability was found in ZZCMS 2023. zzcms · zzcms 2024-08-19 medium5.3 CVE-2024-7924 A vulnerability was found in ZZCMS 2023. zzcms · zzcms 2024-08-19 medium4.9 CVE-2024-43011 An arbitrary file deletion vulnerability exists in the admin/del.php file at line 62 in ZZCMS 2023 and earlier. zzcms · zzcms 2024-08-16 medium4.7 CVE-2024-43009 A reflected cross-site scripting (XSS) vulnerability exists in user/login.php at line 24 in ZZCMS 2023 and earlier. zzcms · zzcms 2024-08-16 medium5.4 CVE-2024-43006 A stored cross-site scripting (XSS) vulnerability exists in ZZCMS2023 in the ask/show.php file at line 21. zzcms · zzcms 2024-08-16 medium4.7 CVE-2024-43005 A reflected cross-site scripting (XSS) vulnerability in the component dl_liuyan_save.php of ZZCMS v2023 allows attackers to execute arbitrary code in the conte… zzcms · zzcms 2024-08-16 medium6.1 CVE-2023-45909 zzzcms v2.2.0 was discovered to contain an open redirect vulnerability. zzzcms · zzzphp 2023-10-18 medium6.3 CVE-2023-5263 A vulnerability was found in ZZZCMS 2.1.7 and classified as critical. zzzcms · zzzcms 2023-09-29 medium5.4 CVE-2022-44361 An issue was discovered in ZZCMS 2022. zzcms · zzcms 2022-12-07 medium5.3 CVE-2022-40444 ZZCMS 2022 was discovered to contain a full path disclosure vulnerability via the page /admin/index.PHP? zzcms · zzcms 2022-09-22 medium5.3 CVE-2022-40443 An absolute path traversal vulnerability in ZZCMS 2022 allows attackers to obtain sensitive information via a crafted GET request sent to /one/siteinfo.php. zzcms · zzcms 2022-09-22 medium4.8 CVE-2021-46437 An issue was discovered in ZZCMS 2021. zzcms · zzcms 2022-04-08 medium5.3 CVE-2021-45286 Directory Traversal vulnerability exists in ZZCMS 2021 via the skin parameter in 1) index.php, 2) bottom.php, and 3) top_index.php. zzcms · zzcms 2022-02-09 medium6.1 CVE-2020-19042 Cross Site Scripting (XSS) vulnerability exists in zzcms 2019 XSS via a modify action in user/adv.php. zzcms · zzcms 2021-12-13 medium5.4 CVE-2020-19683 A Cross Site Scripting (XSS) exists in ZZZCMS V1.7.1 via an editfile action in save.php. zzzcms · zzzcms 2021-12-09 medium5.4 CVE-2020-35973 An issue was discovered in zzcms2020. zzcms · zzcms 2021-06-03 medium5.4 CVE-2020-20285 There is a XSS in the user login page in zzcms 2019. zzcms · zzcms 2020-12-18 medium6.1 CVE-2018-17413 XSS exists in zzcms v8.3 via the /uploadimg_form.php noshuiyin parameter. zzcms · zzcms 2019-03-07

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.