NetSight

Security Dashboard

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

Reset
19 matching advisories · page 1 of 1Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-38812 RuoYi v4.8.2 is vulnerable to SQL Injection via the /tool/gen/createTable endpoint. 2026-06-15 critical9.1 CVE-2025-70985 Incorrect access control in the update function of RuoYi v4.8.2 allows unauthorized attackers to arbitrarily modify data outside of their scope. ruoyi · ruoyi 2026-01-23 critical9.4 CVE-2025-66916 The snailjob component in RuoYi-Vue-Plus versions 5.5.1 and earlier, interface /snail-job/workflow/check-node-expression can execute QLExpress expressions, but… dromara · ruoyi-vue-plus 2026-01-08 critical10.0 CVE-2024-57521 SQL Injection vulnerability in RuoYi v.4.7.9 and before allows a remote attacker to execute arbitrary code via the createTable function in SqlUtil.java. ruoyi · ruoyi 2025-12-23 critical9.8 CVE-2025-28413 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the SysDictTypeController component ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28412 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the /editSave method in SysNoticeController ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28411 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the editSave method in /tool/gen/editSave ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28410 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the cancelAuthUserAll method does not properly validate whether the requesting us… ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28408 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the selectDeptTree method of the /selectDeptTree/{deptId} endpoint does not prope… ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28406 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the jobLogId parameter ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28405 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the changeStatus method ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2025-28402 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the jobId parameter ruoyi · ruoyi 2025-04-07 critical9.8 CVE-2024-46076 RuoYi v4.7.9 and before has a security flaw that allows escaping from comments within the code generation feature, enabling the injection of malicious code. ruoyi · ruoyi 2024-10-07 critical9.8 CVE-2024-42913 RuoYi CMS v4.7.9 was discovered to contain a SQL injection vulnerability via the job_id parameter at /sasfs1. ruoyi · ruoyi 2024-08-26 critical9.8 CVE-2023-49371 RuoYi vulnerable to SQL injection vulnerability maven · com.ruoyi:ruoyi 2023-12-01 critical9.8 CVE-2021-28411 An issue was discovered in getRememberedSerializedIdentity function in CookieRememberMeManager class in lerry903 RuoYi version 3.4.0, allows remote attackers t… ruoyi · ruoyi 2023-08-11 critical9.8 CVE-2022-48114 RuoYi up to v4.7.5 was discovered to contain a SQL injection vulnerability via the component /tool/gen/createTable. ruoyi · ruoyi 2023-02-02 critical9.8 CVE-2021-38241 Deserialization issue discovered in Ruoyi before 4.6.1 allows remote attackers to run arbitrary code via weak cipher in Shiro framework. ruoyi · ruoyi 2022-12-16 critical9.8 CVE-2022-37158 RuoYi v3.8.3 has a Weak password vulnerability in the management system. iocoder · ruoyi-vue-pro 2022-08-25

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.