NetSight

Security Dashboard

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

Reset
51 matching advisories · page 2 of 2Index updated 9 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2020-18084 Cross Site Scripting (XSS) in yzmCMS v5.2 allows remote attackers to execute arbitrary code by injecting commands into the "referer" field of a POST request to… yzmcms · yzmcms 2021-04-30 medium6.1 CVE-2020-22394 In YzmCMS v5.5 the member contribution function in the editor contains a cross-site scripting (XSS) vulnerability. yzmcms · yzmcms 2020-11-19 medium6.1 CVE-2019-16532 An HTTP Host header injection vulnerability exists in YzmCMS V5.3. yzmcms · yzmcms 2019-09-26 medium6.5 CVE-2019-16678 admin/urlrule/add.html in YzmCMS 5.3 allows CSRF with a resultant denial of service by adding a superseding route. yzmcms · yzmcms 2019-09-21 medium5.4 CVE-2018-16247 YzmCMS 5.1 has XSS via the admin/system_manage/user_config_add.html title parameter. yzmcms · yzmcms 2019-06-20 medium4.8 CVE-2019-9661 Stored XSS exists in YzmCMS 5.2 via the admin/system_manage/user_config_edit.html "value" parameter, yzmcms · yzmcms 2019-03-11 medium4.8 CVE-2019-9660 Stored XSS exists in YzmCMS 5.2 via the admin/category/edit.html "catname" parameter. yzmcms · yzmcms 2019-03-11 medium4.8 CVE-2019-9570 An issue was discovered in YzmCMS 5.2.0. yzmcms · yzmcms 2019-03-05 high8.8 CVE-2018-20015 YzmCMS v5.2 has admin/role/add.html CSRF. yzmcms · yzmcms 2018-12-10 medium4.8 CVE-2018-19849 An issue was discovered in YzmCMS 5.2. yzmcms · yzmcms 2018-12-04 medium6.1 CVE-2018-19092 An issue was discovered in YzmCMS v5.2. yzmcms · yzmcms 2018-11-07 medium4.8 CVE-2018-17044 In YzmCMS 5.1, stored XSS exists via the admin/system_manage/user_config_add.html title parameter. yzmcms · yzmcms 2018-09-14 critical9.8 CVE-2018-11554 The forgotten-password feature in index.php/member/reset/reset_email.html in YzmCMS v3.2 through v3.7 has a Response Discrepancy Information Exposure issue and… yzmcms · yzmcms 2018-06-05 medium6.8 CVE-2018-10224 An issue was discovered in YzmCMS 3.8. yzmcms · yzmcms 2018-04-19 medium6.8 CVE-2018-10223 An issue was discovered in YzmCMS 3.8. yzmcms · yzmcms 2018-04-19 medium4.8 CVE-2018-10026 The WeChat module in YzmCMS 3.7.1 has reflected XSS via the admin/module/init.html echostr parameter, related to the valid function in application/wechat/contr… yzmcms · yzmcms 2018-04-11 high7.2 CVE-2018-8756 Eval injection in yzmphp/core/function/global.func.php in YzmCMS v3.7.1 allows remote attackers to achieve arbitrary code execution via PHP code in the POST da… yzmcms · yzmcms 2018-03-18 medium5.4 CVE-2018-8078 YzmCMS 3.7 has Stored XSS via the title parameter to advertisement/adver/edit.html. yzmcms · yzmcms 2018-03-13 medium6.1 CVE-2018-7653 In YzmCMS 3.6, index.php has XSS via the a, c, or m parameter. yzmcms · yzmcms 2018-03-04 high7.2 CVE-2018-7579 \application\admin\controller\update_urls.class.php in YzmCMS 3.6 has SQL Injection via the catids array parameter to admin/update_urls/update_category_url.htm… yzmcms · yzmcms 2018-03-01 medium5.3 CVE-2018-7479 YzmCMS 3.6 allows remote attackers to discover the full path via a direct request to application/install/templates/s1.php. yzmcms · yzmcms 2018-02-26

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.