NetSight

Security Dashboard

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

Reset
51 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.7 CVE-2026-105156 A weakness has been identified in YzmCMS up to 7.6. YzmCMS 48 days ago high7.2 CVE-2026-75417 A SQL injection vulnerability was found in YzmCMS 7.5. 2026-08-28 medium4.3 CVE-2026-15202 A security vulnerability has been detected in YzmCMS up to 7.5. YzmCMS 2026-07-09 medium5.6 CVE-2026-13529 A vulnerability was determined in YzmCMS up to 7.5. YzmCMS 2026-06-29 medium6.1 CVE-2026-29933 A reflected cross-site scripting (XSS) vulnerability in the /index/login.html component of YZMCMS v7.4 allows attackers to execute arbitrary Javascript in the … yzmcms · yzmcms 2026-03-26 medium6.1 CVE-2025-56304 Cross-site scripting (XSS) vulnerability in YzmCMS thru 7.3 via the referer header in the register page. yzmcms · yzmcms 2025-09-23 medium4.3 CVE-2025-3397 A vulnerability classified as problematic has been found in YzmCMS 7.1. yzmcms · yzmcms 2025-04-08 medium6.1 CVE-2024-39174 A cross-site scripting (XSS) vulnerability in the Publish Article function of yzmcms v7.1 allows attackers to execute arbitrary web scripts or HTML via a craft… yzmcms · yzmcms 2024-07-05 medium5.5 CVE-2024-35110 A reflected XSS vulnerability has been found in YzmCMS 7.1. yzmcms · yzmcms 2024-05-17 high7.1 CVE-2024-28725 Cross Site Scripting (XSS) vulnerability in YzmCMS 7.0 allows attackers to run arbitrary code via Ads Management, Carousel Management, and System Settings. yzmcms · yzmcms 2024-05-06 medium6.1 CVE-2024-24291 An issue in the component /member/index/login of yzmcms v7.0 allows attackers to direct users to malicious sites via a crafted URL. yzmcms · yzmcms 2024-02-06 medium6.1 CVE-2023-52274 member/index/register.html in YzmCMS 6.5 through 7.0 allows XSS via the Referer HTTP header. yzmcms · yzmcms 2024-01-11 high8.8 CVE-2020-23595 Cross Site Request Forgery (CSRF) vulnerability in yzmcms version 5.6, allows remote attackers to escalate privileges and gain sensitive information sitemodel/… yzmcms · yzmcms 2023-08-11 medium6.5 CVE-2020-20502 Cross Site Request Forgery found in yzCMS v.2.0 allows a remote attacker to execute arbitrary code via the token check function. yzmcms · yzmcms 2023-06-20 medium5.4 CVE-2021-36712 Cross Site Scripting (XSS) vulnerability in yzmcms 6.1 allows attackers to steal user cookies via image clipping function. yzmcms · yzmcms 2023-02-03 critical9.1 CVE-2022-23383 YzmCMS v6.3 is affected by broken access control. yzmcms · yzmcms 2022-03-10 high8.8 CVE-2022-23384 YzmCMS v6.3 is affected by Cross Site Request Forgery (CSRF) in /admin.add yzmcms · yzmcms 2022-02-15 medium5.3 CVE-2022-23889 The comment function in YzmCMS v6.3 was discovered as being able to be operated concurrently, allowing attackers to create an unusually large number of comment… yzmcms · yzmcms 2022-01-28 high8.8 CVE-2022-23888 YzmCMS v6.3 was discovered to contain a Cross-Site Request Forgey (CSRF) via the component /yzmcms/comment/index/init.html. yzmcms · yzmcms 2022-01-28 medium6.5 CVE-2022-23887 YzmCMS v6.3 was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily delete user accounts via /admin/admin_manage/de… yzmcms · yzmcms 2022-01-28 high8.8 CVE-2020-19951 A cross-site request forgery (CSRF) in /controller/pay.class.php of YzmCMS v5.5 allows attackers to access sensitive components of the application. yzmcms · yzmcms 2021-09-23 medium4.8 CVE-2020-19950 A cross-site scripting (XSS) vulnerability in the /banner/add.html component of YzmCMS v5.3 allows attackers to execute arbitrary web scripts or HTML. yzmcms · yzmcms 2021-09-23 medium4.8 CVE-2020-19949 A cross-site scripting (XSS) vulnerability in the /link/add.html component of YzmCMS v5.3 allows attackers to execute arbitrary web scripts or HTML. yzmcms · yzmcms 2021-09-23 high7.5 CVE-2020-20341 YzmCMS v5.5 contains a server-side request forgery (SSRF) in the grab_image() function. yzmcms · yzmcms 2021-09-01 medium5.4 CVE-2020-19118 Cross Site Scripting (XSS) vulnerabiity in YzmCMS 5.2 via the site_code parameter in admin/index/init.html. yzmcms · yzmcms 2021-07-30 medium4.3 CVE-2020-35972 An issue was discovered in YzmCMS V5.8. yzmcms · yzmcms 2021-06-03 medium5.4 CVE-2020-35971 A storage XSS vulnerability is found in YzmCMS v5.8, which can be used by attackers to inject JS code and attack malicious XSS on the /admin/system_manage/user… yzmcms · yzmcms 2021-06-03 high7.5 CVE-2020-35970 An issue was discovered in YzmCMS 5.8. yzmcms · yzmcms 2021-06-03 medium5.4 CVE-2020-23370 In YzmCMS 5.6, stored XSS exists via the common/static/plugin/ueditor/1.4.3.3/php/controller.php action parameter, which allows remote attackers to upload a sw… yzmcms · yzmcms 2021-05-10 medium6.1 CVE-2020-23369 In YzmCMS 5.6, XSS was discovered in member/member_content/init.html via the SRC attribute of an IFRAME element because of using UEditor 1.4.3.3. yzmcms · yzmcms 2021-05-10

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.