NetSight

Security Dashboard

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

Reset
127 matching advisories · page 4 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2018-17415 zzcms V8.3 has a SQL injection in /user/zs_elite.php via the id parameter. zzcms · zzcms 2019-03-07 high8.8 CVE-2018-17414 zzcms v8.3 has a SQL injection in /user/jobmanage.php via the bigclass parameter. zzcms · zzcms 2019-03-07 medium6.1 CVE-2018-17413 XSS exists in zzcms v8.3 via the /uploadimg_form.php noshuiyin parameter. zzcms · zzcms 2019-03-07 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 high8.8 CVE-2019-9182 There is a CSRF in ZZZCMS zzzphp V1.6.1 via a /admin015/save.php?act=editfile request. zzzcms · zzzphp 2019-02-26 high8.8 CVE-2019-9082 ThinkPHP Remote Code Execution VulnerabilityExploited thinkphp · thinkphp, opensourcebms · open_source_background_management_system, zzzcms · zzzphp 2019-02-24 medium5.4 CVE-2019-9078 zzcms 2019 has XSS via an arbitrary user/ask.php?do=modify parameter because inc/stopsqlin.php does not block a mixed-case string such as sCrIpT. zzcms · zzcms 2019-02-24 high7.2 CVE-2019-9041 An issue was discovered in ZZZCMS zzzphp V1.6.1. zzzcms · zzzphp 2019-02-23 high7.5 CVE-2019-8411 admin/dl_data.php in zzcms 2018 (2018-10-19) allows remote attackers to delete arbitrary files via action=del&filename=../ directory traversal. zzcms · zzcms 2019-02-17 high7.5 CVE-2018-20127 An issue was discovered in zzzphp cms 1.5.8. zzzcms · zzzphp 2018-12-13 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 high7.2 CVE-2018-18790 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 high7.2 CVE-2018-18788 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 critical9.8 CVE-2018-18787 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 critical9.8 CVE-2018-18786 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 critical9.8 CVE-2018-18785 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 high7.2 CVE-2018-18784 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-10-29 medium6.5 CVE-2018-17798 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-09-30 medium6.5 CVE-2018-17797 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-09-30 critical9.8 CVE-2018-17136 zzcms 8.3 contains a SQL Injection vulnerability in /user/check.php via a Client-Ip HTTP header. zzcms · zzcms 2018-09-17 high7.5 CVE-2018-16344 An issue was discovered in zzcms 8.3. zzcms · zzcms 2018-09-02 critical9.8 CVE-2018-1000653 zzcms version 8.3 and earlier contains a SQL Injection vulnerability in zt/top.php line 5 that can result in could be attacked by sql injection in zzcms in ngi… zzcms · zzcms 2018-08-20 high8.8 CVE-2018-14963 zzcms 8.3 has CSRF via the admin/adminadd.php?action=add URI. zzcms · zzcms 2018-08-06 medium5.4 CVE-2018-14962 zzcms 8.3 has stored XSS related to the content variable in user/manage.php and zt/show.php. zzcms · zzcms 2018-08-06 critical9.8 CVE-2018-14961 dl/dl_sendmail.php in zzcms 8.3 has SQL Injection via the sql parameter. zzcms · zzcms 2018-08-06 critical9.8 CVE-2018-13116 /user/del.php in zzcms 8.3 allows SQL injection via the tablename parameter after leveraging use of the zzcms_ask table. zzcms · zzcms 2018-07-03 high7.5 CVE-2018-13056 An issue was discovered on zzcms 8.3. zzcms · zzcms 2018-07-02 high7.5 CVE-2018-9331 An issue was discovered in zzcms 8.2. zzcms · zzcms 2018-04-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.