NetSight

Security Dashboard

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

Reset
114 matching advisories · page 2 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2026-37216 Ruoyi 4.8.2 is vulnerable to Cross Site Scripting (XSS) at the interface /system/notice/add. 2026-06-15 medium6.3 CVE-2026-9374 A vulnerability was found in yangzongzhuan RuoYi-Vue up to 3.9.2. yangzongzhuan RuoYi-Vue 2026-05-24 medium4.7 CVE-2026-4564 A security vulnerability has been detected in yangzongzhuan RuoYi up to 4.8.2. yangzongzhuan RuoYi 2026-03-23 medium6.3 CVE-2026-2819 A vulnerability was identified in Dromara RuoYi-Vue-Plus up to 5.5.3. Dromara RuoYi-Vue-Plus 2026-02-20 high7.5 CVE-2025-70986 Incorrect access control in the selectDept function of RuoYi v4.8.2 allows unauthorized attackers to arbitrarily access sensitive department data. ruoyi · ruoyi 2026-01-23 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 medium6.3 CVE-2025-14856 A security vulnerability has been detected in y_project RuoYi up to 4.8.1. ruoyi · ruoyi 2025-12-18 medium4.6 CVE-2025-67342 RuoYi versions 4.8.1 and earlier is affected by a stored XSS vulnerability in the /system/menu/edit endpoint. ruoyi · ruoyi 2025-12-12 high7.5 CVE-2025-46175 Ruoyi v4.8.0 is vulnerable to Incorrect Access Control. ruoyi · ruoyi 2025-11-26 high8.8 CVE-2025-56396 An issue was discovered in Ruoyi 4.8.1 allowing attackers to gain escalated privileges due to the owning department having higher rights than the active user. ruoyi · ruoyi 2025-11-26 high7.5 CVE-2025-46174 Ruoyi v4.8.0 vulnerable to Incorrect Access Control. ruoyi · ruoyi 2025-11-26 medium6.3 CVE-2025-10989 A security flaw has been discovered in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-09-26 medium6.3 CVE-2025-10988 A vulnerability was identified in YunaiV ruoyi-vue-pro up to 2025.09. iocoder · ruoyi-vue-pro 2025-09-26 medium6.3 CVE-2025-10473 A security flaw has been discovered in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-09-15 medium5.4 CVE-2025-10384 A flaw has been found in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-09-13 medium6.3 CVE-2025-10278 A flaw has been found in YunaiV ruoyi-vue-pro up to 2025.09. iocoder · ruoyi-vue-pro 2025-09-12 medium6.3 CVE-2025-10276 A security vulnerability has been detected in YunaiV ruoyi-vue-pro up to 2025.09. iocoder · ruoyi-vue-pro 2025-09-12 medium6.3 CVE-2025-10218 A flaw has been found in lostvip-com ruoyi-go 2.1. lostvip · ruoyi-go 2025-09-10 medium6.3 CVE-2025-9413 A flaw has been found in lostvip-com ruoyi-go up to 2.1. lostvip · ruoyi-go 2025-08-25 medium6.3 CVE-2025-9412 A vulnerability was detected in lostvip-com ruoyi-go up to 2.1. lostvip · ruoyi-go 2025-08-25 medium6.3 CVE-2025-9411 A security vulnerability has been detected in lostvip-com ruoyi-go up to 2.1. lostvip · ruoyi-go 2025-08-25 medium6.3 CVE-2025-9410 A weakness has been identified in lostvip-com ruoyi-go up to 2.1. lostvip · ruoyi-go 2025-08-25 medium4.3 CVE-2025-9409 A security flaw has been discovered in lostvip-com ruoyi-go up to 2.1. lostvip · ruoyi-go 2025-08-25 low3.5 CVE-2025-8847 A vulnerability was found in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-08-11 medium4.3 CVE-2025-7907 A vulnerability was found in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-07-20 medium6.3 CVE-2025-7906 A vulnerability was found in yangzongzhuan RuoYi up to 4.8.1 and classified as critical. ruoyi · ruoyi 2025-07-20 medium4.3 CVE-2025-7903 A vulnerability classified as problematic was found in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-07-20 low3.5 CVE-2025-7902 A vulnerability classified as problematic has been found in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-07-20

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.