NetSight

Security Dashboard

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

Reset
114 matching advisories · page 4 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.7 CVE-2025-0734 A vulnerability has been found in y_project RuoYi up to 4.8.0 and classified as critical. ruoyi · ruoyi 2025-01-27 medium6.3 CVE-2024-54762 Ruoyi v.4.7.9 and before contains an authenticated SQL injection vulnerability. ruoyi · ruoyi 2025-01-09 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 low3.1 CVE-2024-9048 A vulnerability was found in y_project RuoYi up to 4.7.9. ruoyi · ruoyi 2024-09-21 medium6.1 CVE-2024-42900 Ruoyi v4.7.9 and before was discovered to contain a cross-site scripting (XSS) vulnerability via the sql parameter of the createTable() function at /tool/gen/c… ruoyi · ruoyi 2024-08-28 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 medium6.1 CVE-2024-41599 Cross Site Scripting vulnerability in RuoYi v.4.7.9 and before allows a remote attacker to execute arbitrary code via the file upload method ruoyi · ruoyi 2024-07-19 low3.5 CVE-2024-6511 A vulnerability classified as problematic was found in y_project RuoYi up to 4.7.9. ruoyi · ruoyi 2024-07-04 high7.5 CVE-2024-29400 An issue was discovered in RuoYi v4.5.1, allows attackers to obtain sensitive information via the status parameter. ruoyi · ruoyi 2024-04-12 medium4.7 CVE-2023-52048 RuoYi v4.7.8 was discovered to contain a cross-site scripting (XSS) vulnerability via the component /system/notice/. ruoyi · ruoyi 2024-02-28 medium4.3 CVE-2023-7133 A vulnerability was found in y_project RuoYi 4.7.8. ruoyi · ruoyi 2023-12-28 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 low3.5 CVE-2023-3815 RuoYi vulnerable to Cross-site Scripting maven · com.ruoyi:ruoyi 2023-07-21 low3.5 CVE-2023-3163 RuoYi Uncontrolled Resource Consumption vulnerability maven · com.ruoyi:ruoyi 2023-06-08 high7.5 CVE-2023-27025 RuoYi vulnerable to arbitrary file download maven · com.ruoyi:ruoyi 2023-04-02 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 medium5.5 CVE-2022-4566 A vulnerability, which was classified as critical, has been found in y_project RuoYi 4.7.5. ruoyi · ruoyi 2022-12-16 medium6.1 CVE-2022-4348 RuoYi-Cloud Cross-site Scripting vulnerability maven · com.ruoyi:ruoyi-common 2022-12-08 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 medium5.4 CVE-2022-32065 RuoYi 4.7.3 vulnerable to arbitrary file upload in background management module maven · com.ruoyi:ruoyi 2022-07-13 medium6.5 CVE-2022-23869 In RuoYi v4.7.2 through the WebUI, user test1 does not have permission to reset the password of user test3, but the password of user test3 can be reset through… ruoyi · ruoyi 2022-03-30 high7.8 CVE-2022-23868 RuoYi v4.7.2 contains a CSV injection vulnerability through ruoyi-admin when a victim opens .xlsx log file. ruoyi · ruoyi 2022-03-30

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.