NetSight

Security Dashboard

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

Reset
28 matching advisories · page 1 of 1Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2026-121583 A vulnerability was identified in Sanluan PublicCMS 5. This affects the function... Sanluan · PublicCMS, sanluan · PublicCMS 18 days ago medium6.3 CVE-2026-120319 A vulnerability was found in Sanluan PublicCMS 4.x/5.x/6.x. This affects the function... sanluan · PublicCMS 20 days ago medium4.3 CVE-2026-110113 PublicCMS through V6.202608.a contains an insecure direct object reference vulnerability in the TradeAddressController tradeAddress/save handler that allows au… PublicCMS 39 days ago medium4.3 CVE-2026-109160 A vulnerability was determined in PublicCMS up to 5.202608.a. PublicCMS 39 days ago medium6.1 CVE-2026-36521 PublicCMS V5.202506.d has a Cross Site Scripting (XSS) vulnerability in the site configuration management module. 2026-06-15 medium6.3 CVE-2026-8740 A flaw has been found in Sanluan PublicCMS 5.202506.d. 2026-05-17 medium5.3 CVE-2026-8739 A vulnerability was detected in Sanluan PublicCMS 5.202506.d. 2026-05-17 medium6.5 CVE-2026-8738 A security vulnerability has been detected in Sanluan PublicCMS 5.202506.d. 2026-05-17 medium5.3 CVE-2026-8737 A weakness has been identified in Sanluan PublicCMS 5.202506.d. 2026-05-17 medium4.3 CVE-2026-6797 A vulnerability was identified in Sanluan PublicCMS up to 6.202506.d. Sanluan PublicCMS 2026-04-21 medium4.3 CVE-2026-6796 A vulnerability was determined in Sanluan PublicCMS up to 6.202506.d. Sanluan PublicCMS 2026-04-21 medium4.7 CVE-2026-5987 A security vulnerability has been detected in Sanluan PublicCMS up to 6.202506.d. Sanluan PublicCMS 2026-04-09 medium6.3 CVE-2026-3289 A weakness has been identified in Sanluan PublicCMS 6.202506.d. publiccms · publiccms 2026-02-27 medium4.2 CVE-2026-2010 A vulnerability has been found in Sanluan PublicCMS up to 4.0.202506.d/5.202506.d/6.202506.d. publiccms · publiccms 2026-02-06 medium5.4 CVE-2026-1112 A vulnerability was found in Sanluan PublicCMS up to 5.202506.d. publiccms · publiccms 2026-01-18 medium4.7 CVE-2026-1111 A vulnerability has been found in Sanluan PublicCMS up to 5.202506.d. publiccms · publiccms 2026-01-18 medium5.4 CVE-2025-65837 PublicCMS V5.202506.b is vulnerable to Cross Site Scripting (XSS) in the Content Search module. publiccms · publiccms 2025-12-22 medium4.8 CVE-2024-46410 PublicCMS V4.0.202406.d was discovered to contain a cross-site scripting (XSS) vulnerability via a crafted script to the Category Managment feature publiccms · publiccms 2024-10-08 medium6.5 CVE-2024-40547 PublicCMS v4.0.202302.e was discovered to contain an arbitrary file content replacement vulnerability via the component /admin/cmsTemplate/replace. publiccms · publiccms 2024-07-12 medium4.3 CVE-2024-2911 A vulnerability, which was classified as problematic, was found in Tianjin PubliCMS 4.0.202302.e. publiccms · publiccms 2024-03-26 medium5.4 CVE-2023-51252 PublicCMS 4.0 is vulnerable to Cross Site Scripting (XSS). publiccms · publiccms 2024-01-10 medium6.5 CVE-2023-48204 An issue in PublicCMS v.4.0.202302.e allows a remote attacker to obtain sensitive information via the appToken and Parameters parameter of the api/method/getHt… publiccms · publiccms 2023-11-16 medium5.3 CVE-2022-29784 PublicCMS V4.0.202204.a and below contains an information leak via the component /views/directive/sys/SysConfigDataDirective.java. publiccms · publiccms 2022-06-03 medium5.4 CVE-2020-21333 Cross Site Scripting (XSS) vulnerability in PublicCMS 4.0 to get an admin cookie when the Administrator reviews submit case. publiccms · publiccms 2021-07-09 medium4.8 CVE-2018-18927 An issue was discovered in PublicCMS V4.0. publiccms · publiccms 2018-11-04 medium5.3 CVE-2018-17368 An issue was discovered in PublicCMS V4.0.180825. publiccms · publiccms 2018-09-23 medium6.5 CVE-2018-12494 An issue was discovered in PublicCMS V4.0.20180210. publiccms · publiccms 2018-06-15 medium6.5 CVE-2018-12493 An issue was discovered in PublicCMS V4.0.20180210. publiccms · publiccms 2018-06-15

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.