NetSight

Security Dashboard

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

Reset
127 matching advisories · page 2 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2023-5582 A vulnerability, which was classified as problematic, has been found in ZZZCMS 2.2.0. zzzcms · zzzcms 2023-10-14 medium6.3 CVE-2023-5263 A vulnerability was found in ZZZCMS 2.1.7 and classified as critical. zzzcms · zzzcms 2023-09-29 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 high8.8 CVE-2023-36162 Cross Site Request Forgery vulnerability in ZZCMS v.2023 and earlier allows a remote attacker to gain privileges via the add function in adminlist.php. zzcms · zzcms 2023-07-03 medium5.4 CVE-2022-44361 An issue was discovered in ZZCMS 2022. zzcms · zzcms 2022-12-07 high7.2 CVE-2022-40447 ZZCMS 2022 was discovered to contain a SQL injection vulnerability via the keyword parameter at /admin/baojia_list.php. zzcms · zzcms 2022-09-22 high7.2 CVE-2022-40446 ZZCMS 2022 was discovered to contain a SQL injection vulnerability via the component /admin/sendmailto.php?tomail=&groupid=. zzcms · zzcms 2022-09-22 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 high7.2 CVE-2019-12359 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high8.8 CVE-2019-12358 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high7.2 CVE-2019-12357 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high8.8 CVE-2019-12356 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high8.8 CVE-2019-12355 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high7.2 CVE-2019-12354 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high7.2 CVE-2019-12353 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 high8.8 CVE-2019-12352 An issue was discovered in zzcms 2019. zzcms · zzcms 2022-06-17 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 medium4.8 CVE-2021-46437 An issue was discovered in ZZCMS 2021. zzcms · zzcms 2022-04-08 high7.2 CVE-2021-46436 An issue was discovered in ZZCMS 2021. zzcms · zzcms 2022-04-08 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 high7.5 CVE-2021-45347 An Incorrect Access Control vulnerability exists in zzcms 8.2, which lets a malicious user bypass authentication by changing the user name in the cookie to use… zzcms · zzcms 2022-02-14 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 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 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 high8.8 CVE-2020-19682 A Cross Site Request Forgery (CSRF) vulnerability exits in ZZZCMS V1.7.1 via the save_user funciton in save.php. zzzcms · zzzcms 2021-12-09 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

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.