NetSight

Security Dashboard

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

Reset
64 matching advisories · page 2 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2020-19915 Cross Site Scripting (XSS vulnerability exists in WUZHI CMS 4.1.0 via the mailbox username in index.php. wuzhicms · wuzhicms 2021-09-20 critical9.8 CVE-2021-40674 An SQL injection vulnerability exists in Wuzhi CMS v4.1.0 via the KeyValue parameter in coreframe/app/order/admin/index.php. wuzhicms · wuzhicms 2021-09-20 critical9.8 CVE-2021-40670 SQL Injection vulnerability exists in Wuzhi CMS 4.1.0 via the keywords iparameter under the /coreframe/app/order/admin/card.php file. wuzhicms · wuzhicms 2021-09-16 critical9.8 CVE-2021-40669 SQL Injection vulnerability exists in Wuzhi CMS 4.1.0 via the keywords parameter under the coreframe/app/promote/admin/index.php file. wuzhicms · wuzhicms 2021-09-16 high7.5 CVE-2020-18877 SQL Injection in Wuzhi CMS v4.1.0 allows remote attackers to obtain sensitive information via the 'flag' parameter in the component '/coreframe/app/order/admin… wuzhicms · wuzhicms 2021-08-20 medium6.1 CVE-2020-18654 Cross Site Scripting (XSS) in Wuzhi CMS v4.1.0 allows remote attackers to execute arbitrary code via the "Title" parameter in the component "/coreframe/app/gue… wuzhicms · wuzhicms 2021-06-22 medium4.3 CVE-2020-21590 Directory traversal in coreframe/app/template/admin/index.php in WUZHI CMS 4.1.0 allows attackers to list files in arbitrary directories via the dir parameter. wuzhicms · wuzhicms 2021-04-02 medium5.4 CVE-2018-17426 WUZHI CMS 4.1.0 has stored XSS via the "Extension module" "SMS in station" field under the index.php?m=core URI. wuzhicms · wuzhicms 2019-03-07 medium5.4 CVE-2018-17425 WUZHI CMS 4.1.0 has stored XSS via the "Membership Center" "I want to ask" "detailed description" field under the index.php?m=member URI. wuzhicms · wuzhicms 2019-03-07 medium6.1 CVE-2019-9110 XSS exists in WUZHI CMS 4.1.0 via index.php?m=content&f=postinfo&v=listing&set_iframe=[XSS] to coreframe/app/content/postinfo.php. wuzhicms · wuzhicms 2019-02-25 medium6.1 CVE-2019-9109 XSS exists in WUZHI CMS 4.1.0 via index.php?m=message&f=message&v=add&username=[XSS] to coreframe/app/message/message.php. wuzhicms · wuzhicms 2019-02-25 medium6.1 CVE-2019-9108 XSS exists in WUZHI CMS 4.1.0 via index.php?m=core&f=map&v=baidumap&x=[XSS]&y=[XSS] to coreframe/app/core/map.php. wuzhicms · wuzhicms 2019-02-25 medium6.1 CVE-2019-9107 XSS exists in WUZHI CMS 4.1.0 via index.php?m=attachment&f=imagecut&v=init&imgurl=[XSS] to coreframe/app/attachment/imagecut.php. wuzhicms · wuzhicms 2019-02-25 critical9.8 CVE-2018-20572 WUZHI CMS 4.1.0 allows coreframe/app/coupon/admin/copyfrom.php SQL injection via the index.php?m=promote&f=index&v=search keywords parameter, a related issue t… wuzhicms · wuzhicms 2018-12-28 medium4.8 CVE-2018-18938 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-11-05 high8.8 CVE-2018-18712 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-10-29 high8.8 CVE-2018-18711 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-10-29 medium6.1 CVE-2018-17832 XSS exists in WUZHI CMS 2.0 via the index.php v or f parameter. wuzhicms · wuzhi_cms 2018-10-01 medium6.1 CVE-2018-14512 An XSS vulnerability was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-07-23 high7.2 CVE-2018-14472 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-07-20 critical9.8 CVE-2018-11722 WUZHI CMS 4.1.0 has a SQL Injection in api/uc.php via the 'code' parameter, because 'UC_KEY' is hard coded. wuzhicms · wuzhicms 2018-06-05 medium5.4 CVE-2018-11549 An issue was discovered in WUZHI CMS 4.1.0 There is a Stored XSS Vulnerability in "Account Settings -> Member Centre -> Chinese information -> Ordinary member"… wuzhicms · wuzhicms 2018-05-29 critical9.8 CVE-2018-11528 WUZHI CMS 4.1.0 has SQL Injection via an api/sms_check.php?param= URI. wuzhicms · wuzhicms 2018-05-29 high8.8 CVE-2018-11493 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-05-26 medium4.8 CVE-2018-10391 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-04-26 medium4.8 CVE-2018-10368 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-04-25 medium4.8 CVE-2018-10367 An issue was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-04-25 medium5.4 CVE-2018-10313 WUZHI CMS 4.1.0 allows persistent XSS via the form%5Bqq_10%5D parameter to the /index.php?m=member&f=index&v=profile&set_iframe=1 URI. wuzhicms · wuzhicms 2018-04-24 high8.8 CVE-2018-10312 index.php?m=member&v=pw_reset in WUZHI CMS 4.1.0 allows CSRF to change the password of a common member. wuzhicms · wuzhicms 2018-04-24 medium6.1 CVE-2018-10311 A vulnerability was discovered in WUZHI CMS 4.1.0. wuzhicms · wuzhicms 2018-04-24

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.