NetSight

Security Dashboard

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

Reset
39 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2025-22957 A SQL injection vulnerability exists in the front-end of the website in ZZCMS <= 2023, which can be exploited without any authentication. zzcms · zzcms 2025-01-31 critical9.8 CVE-2024-52724 ZZCMS 2023 was discovered to contain a SQL injection vulnerability in /q/show.php. zzcms · zzcms 2024-12-02 critical9.8 CVE-2023-50104 ZZCMS 2023 has a file upload vulnerability in 3/E_bak5.1/upload/index.php, allowing attackers to exploit this loophole to gain server privileges and execute ar… zzcms · zzcms 2023-12-29 critical9.8 CVE-2023-45554 File Upload vulnerability in zzzCMS v.2.1.9 allows a remote attacker to execute arbitrary code via modification of the imageext parameter from jpg, jpeg,gif, a… zzzcms · zzzcms 2023-10-25 critical9.8 CVE-2023-42398 An issue in zzCMS v.2023 allows a remote attacker to execute arbitrary code and obtain sensitive information via the ueditor component in controller.php. zzcms · zzcms 2023-09-15 critical9.8 CVE-2019-12351 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-02 critical9.8 CVE-2019-12350 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-02 critical9.8 CVE-2019-12349 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-02 critical9.8 CVE-2022-23881 ZZZCMS zzzphp v2.1.0 was discovered to contain a remote command execution (RCE) vulnerability via danger_key() at zzz_template.php. zzzcms · zzzphp 2022-03-23 critical9.8 CVE-2021-42945 A SQL Injection vulnerability exists in ZZCMS 2021 via the askbigclassid parameter in /admin/ask.php. zzcms · zzcms 2021-12-15 critical9.8 CVE-2021-43703 An Incorrect Access Control vulnerability exists in zzcms less than or equal to 2019 via admin.php. zzcms · zzcms 2021-12-09 critical9.8 CVE-2019-12348 An issue was discovered in zzcms 2019. zzcms · zzcms 2021-05-24 critical9.8 CVE-2021-32605 zzzcms zzzphp before 2.0.4 allows remote attackers to execute arbitrary OS commands by placing them in the keys parameter of a ?location=search URI, as demonst… zzzcms · zzzphp 2021-05-11 critical9.8 CVE-2020-23426 zzcms 201910 contains an access control vulnerability through escalation of privileges in /user/adv.php, which allows an attacker to modify data for further at… zzcms · zzcms 2021-04-08 critical9.8 CVE-2020-24877 A SQL injection vulnerability in zzzphp v1.8.0 through /form/index.php?module=getjson may lead to a possible access restriction bypass. zzzcms · zzzphp 2021-03-15 critical9.8 CVE-2020-18717 SQL Injection in ZZZCMS zzzphp 1.7.1 allows remote attackers to execute arbitrary code due to a lack of parameter filtering in inc/zzz_template.php. zzzcms · zzzphp 2021-02-05 critical9.8 CVE-2020-20298 Eval injection vulnerability in the parserCommom method in the ParserTemplate class in zzz_template.php in zzzphp 1.7.2 allows remote attackers to execute arbi… zzzcms · zzzphp 2020-12-18 critical9.8 CVE-2019-17408 parserIfLabel in inc/zzz_template.php in ZZZCMS zzzphp 1.7.3 allows remote attackers to execute arbitrary code because the danger_key function can be bypassed … zzzcms · zzzphp 2019-10-14 critical9.8 CVE-2019-16722 ZZZCMS zzzphp v1.7.2 has an insufficient protection mechanism against PHP Code Execution, because passthru bypasses an str_ireplace operation. zzzcms · zzzphp 2019-09-23 critical9.8 CVE-2019-1010153 zzcms 8.3 and earlier is affected by: SQL Injection. zzcms · zzcms 2019-07-23 critical9.8 CVE-2019-1010152 zzcms 8.3 and earlier is affected by: File Delete to Code Execution. zzcms · zzcms 2019-07-23 critical9.8 CVE-2019-1010150 zzcms 8.3 and earlier is affected by: File Delete to Code Execution. zzcms · zzcms 2019-07-23 critical9.8 CVE-2019-1010149 zzcms version 8.3 and earlier is affected by: File Delete to Code Execution. zzcms · zzcms 2019-07-23 critical9.8 CVE-2019-1010148 zzcms version 8.3 and earlier is affected by: SQL Injection. zzcms · zzcms 2019-07-23 critical9.8 CVE-2019-1010151 zzcms zzmcms 8.3 and earlier is affected by: File Delete to getshell. zzcms · zzmcms 2019-07-19 critical9.8 CVE-2019-10647 ZZZCMS zzzphp v1.6.3 allows remote attackers to execute arbitrary PHP code via a .php URL in the plugins/ueditor/php/controller.php?action=catchimage source[] … zzzcms · zzzphp 2019-03-30 critical9.8 CVE-2018-17412 zzcms v8.3 contains a SQL Injection vulnerability in /user/logincheck.php via an X-Forwarded-For HTTP header. zzcms · zzcms 2019-03-07 critical9.8 CVE-2018-18792 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 critical9.8 CVE-2018-18791 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 critical9.8 CVE-2018-18789 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29

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.