NetSight

Security Dashboard

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

Reset
114 matching advisories · page 3 of 4Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2025-7901 A vulnerability was found in yangzongzhuan RuoYi up to 4.8.1. ruoyi · ruoyi 2025-07-20 medium5.3 CVE-2025-6925 A vulnerability has been found in Dromara RuoYi-Vue-Plus 5.4.0 and classified as critical. dromara · ruoyi-vue-plus 2025-06-30 medium6.3 CVE-2025-6466 A vulnerability was found in ageerle ruoyi-ai 2.0.0 and classified as critical. ageerle · ruoyi-ai 2025-06-22 low3.1 CVE-2025-4819 A vulnerability classified as problematic has been found in y_project RuoYi 4.8.0. ruoyi · ruoyi 2025-05-17 low3.1 CVE-2025-4537 A vulnerability was found in yangzongzhuan RuoYi-Vue up to 3.8.9 and classified as problematic. ruoyi · ruoyi-vue 2025-05-11 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 high8.8 CVE-2025-28409 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the add method of the /add/{parentId} endpoint does not properly validate whether… 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 high8.8 CVE-2025-28407 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the edit method of the /edit/{dictId} endpoint does not properly validate whether… 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 high7.2 CVE-2025-28403 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the editSave method does not properly validate whether the requesting user has ad… 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 medium6.7 CVE-2025-28401 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the menuId parameter ruoyi · ruoyi 2025-04-07 medium6.7 CVE-2025-28400 An issue in RUoYi v.4.8.0 allows a remote attacker to escalate privileges via the postID parameter in the edit method ruoyi · ruoyi 2025-04-07 high7.3 CVE-2025-3202 A vulnerability classified as critical has been found in ageerle ruoyi-ai up to 2.0.0. ageerle · ruoyi-ai 2025-04-04 high7.3 CVE-2025-3199 A vulnerability was found in ageerle ruoyi-ai up to 2.0.1 and classified as critical. pandarobot · ruoyi_ai 2025-04-04 medium5.4 CVE-2025-2744 A vulnerability, which was classified as critical, was found in zhijiantianya ruoyi-vue-pro 2.4.1. iocoder · ruoyi-vue-pro 2025-03-25 medium4.3 CVE-2025-2743 A vulnerability, which was classified as problematic, has been found in zhijiantianya ruoyi-vue-pro 2.4.1. iocoder · ruoyi-vue-pro 2025-03-25 medium5.4 CVE-2025-2742 A vulnerability classified as critical was found in zhijiantianya ruoyi-vue-pro 2.4.1. iocoder · ruoyi-vue-pro 2025-03-25 medium5.4 CVE-2025-2708 A vulnerability was identified in zhijiantianya ruoyi-vue-pro 2.4.1. iocoder · ruoyi-vue-pro 2025-03-24 medium5.4 CVE-2025-2707 A vulnerability was determined in zhijiantianya ruoyi-vue-pro 2.4.1. iocoder · ruoyi-vue-pro 2025-03-24 medium6.3 CVE-2025-2040 A vulnerability classified as critical was found in zhijiantianya ruoyi-vue-pro 2.4.1. iocoder · ruoyi-vue-pro 2025-03-06 medium4.9 CVE-2024-57439 RuoYi vulnerable to Denial of Service by attackers with admin privileges maven · com.ruoyi:ruoyi 2025-01-29 medium5.7 CVE-2024-57438 RuoYi has insecure permissions maven · com.ruoyi:ruoyi 2025-01-29 medium6.5 CVE-2024-57437 RuoYi v4.8.0 was discovered to contain a SQL injection vulnerability via the orderby parameter at /monitor/online/list. ruoyi · ruoyi 2025-01-29 high7.2 CVE-2024-57436 RuoYi allowed unauthorized attackers to view the session ID of the admin in the system monitoring maven · com.ruoyi:ruoyi 2025-01-29

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.