NetSight

Security Dashboard

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

Reset
23 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.3 CVE-2026-126998 A security flaw has been discovered in JeecgBoot up to 3.9.5. This vulnerability affects the... n/a · JeecgBoot 9 days ago high7.3 CVE-2026-126997 A vulnerability was identified in JeecgBoot up to 3.9.6. This affects the function RestTemplate... n/a · JeecgBoot 9 days ago high7.3 CVE-2026-124554 A security flaw has been discovered in JeecgBoot 3.9.5. This affects an unknown part of the file ... n/a · JeecgBoot 13 days ago high8.1 CVE-2026-108657 JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the SysTenantController passApply handler that allows any authenticated user to appro… JeecgBoot 42 days ago high8.1 CVE-2026-108628 JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the saveDeptRolePermission endpoint of SysDepartPermissionController that allows any … JeecgBoot 42 days ago high7.1 CVE-2026-108623 JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the SysLogController deleteBatch handler that allows any authenticated user to delete… JeecgBoot 42 days ago high7.3 CVE-2026-19000 A vulnerability was identified in JeecgBoot up to 3.9.2. JeecgBoot 2026-08-06 high8.6 CVE-2026-58377 JeecgBoot through 3.9.2 contains a broken access control vulnerability that allows authenticated low-privilege users to perform full create, read, update, and … n/a · JeecgBoot 2026-06-30 high8.7 CVE-2026-58375 JimuReport through 2.5.0 exposes the POST /jmreport/auto/export endpoint without authentication: the handler is annotated @JimuNoLoginRequired, so JimuReportTo… jeecgboot · JimuReport 2026-06-30 high7.3 CVE-2026-9580 A vulnerability was determined in JeecgBoot up to 3.9.1. JeecgBoot 2026-05-26 high7.3 CVE-2026-5616 A security vulnerability has been detected in JeecgBoot 3.9.0/3.9.1. 2026-04-06 high7.5 CVE-2024-57606 SQL injection in JeecgBoot maven · org.jeecgframework.boot:jeecg-boot-common 2025-02-07 high7.5 CVE-2023-41578 Jeecg boot arbitrary file read vulnerability maven · org.jeecgframework.boot:jeecg-boot-parent 2023-09-08 high7.5 CVE-2023-34603 JeecgBoot vulnerable to SQL injection in queryFilterTableDictInfo maven · org.jeecgframework.boot:jeecg-boot-parent 2023-06-19 high7.5 CVE-2023-34602 JeecgBoot vulnerable to SQL injection in queryTableDictItemsByCode maven · org.jeecgframework.boot:jeecg-boot-parent 2023-06-19 high7.5 CVE-2023-33510 Jeecg P3 Biz Chat allows remote attackers to read arbitrary files maven · org.jeecgframework.p3:jeecg-p3-biz-chat 2023-06-07 high8.8 CVE-2023-24789 jeecg-boot contains SQL Injection vulnerability maven · org.jeecgframework.boot:jeecg-boot-parent 2023-03-06 high7.5 CVE-2021-37306 Insecure Permissions issue in jeecg-boot maven · org.jeecgframework.boot:jeecg-boot-base 2023-02-03 high7.5 CVE-2021-37305 Insecure Permissions issue in jeecg-boot maven · org.jeecgframework.boot:jeecg-boot-base 2023-02-03 high7.5 CVE-2021-37304 Insecure Permissions issue in jeecg-boot maven · org.jeecgframework.boot:jeecg-boot-base 2023-02-03 high7.3 CVE-2022-2647 A vulnerability was found in jeecg-boot. jeecg · jeecg_boot 2022-08-04 high7.5 CVE-2020-20948 An arbitrary file download vulnerability in jeecg v3.8 allows attackers to access sensitive files via modification of the "localPath" variable. jeecg · jeecg 2021-12-27 high7.5 CVE-2020-28087 A SQL injection vulnerability in /jeecg boot/sys/dict/loadtreedata of jeecg-boot CMS 2.3 allows attackers to access sensitive database information. jeecg · jeecg_boot 2021-08-06

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.