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 just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2026-1552 A security vulnerability has been detected in SEMCMS 5.0. sem-cms · semcms 2026-01-29 medium5.4 CVE-2025-51660 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the lgid parameter at SEMCMS_Products.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51659 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_Products.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51658 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_InquiryView.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51657 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the lgid parameter at SEMCMS_Link.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51656 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_Link.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51655 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Quanxian.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51654 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Infocategories.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51653 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_ct.php. sem-cms · semcms 2025-07-14 medium5.4 CVE-2025-51652 SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Categories.php. sem-cms · semcms 2025-07-14 medium6.3 CVE-2024-13193 A vulnerability has been found in SEMCMS up to 4.8 and classified as critical. sem-cms · semcms 2025-01-08 medium4.9 CVE-2024-52725 SemCms v4.8 was discovered to contain a SQL injection vulnerability. sem-cms · semcms 2024-11-20 medium5.9 CVE-2024-36801 A SQL injection vulnerability in SEMCMS v.4.8, allows a remote attacker to obtain sensitive information via the lgid parameter in Download.php. sem-cms · semcms 2024-06-04 medium6.3 CVE-2024-4595 A vulnerability has been found in SEMCMS up to 4.8 and classified as critical. sem-cms · semcms 2024-05-07 medium6.5 CVE-2024-31009 SQL injection vulnerability in SEMCMS v.4.8, allows a remote attacker to obtain sensitive information via lgid parameter in Banner.php. sem-cms · semcms 2024-04-03 medium6.1 CVE-2021-38728 SEMCMS SHOP v 1.1 is vulnerable to Cross Site Scripting (XSS) via Ant_M_Coup.php. sem-cms · semcms 2022-10-28 medium6.3 CVE-2022-2726 A vulnerability classified as critical has been found in SEMCMS. sem-cms · semcms 2022-08-09 medium4.8 CVE-2018-20017 SEMCMS 3.5 has XSS via the first text box to the SEMCMS_Main.php URI. sem-cms · semcms 2018-12-10 medium4.8 CVE-2018-18841 XSS was discovered in SEMCMS PHP V3.4 via the SEMCMS_SeoAndTag.php?Class=edit&CF=SeoAndTag tag_indexkey parameter. sem-cms · semcms 2018-10-30 medium5.4 CVE-2018-18840 XSS was discovered in SEMCMS PHP V3.4 via the SEMCMS_SeoAndTag.php?Class=edit&CF=SeoAndTag tag_indexmetatit parameter. sem-cms · semcms 2018-10-30 medium6.1 CVE-2018-18783 XSS was discovered in SEMCMS V3.4 via the semcms_remail.php?type=ok umail parameter. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18745 An XSS issue was discovered in SEMCMS 3.4 via admin/SEMCMS_Menu.php?lgid=1 during editing. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18744 An XSS issue was discovered in SEMCMS 3.4 via the fifth text box to the admin/SEMCMS_Main.php URI. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18743 An XSS issue was discovered in SEMCMS 3.4 via the second text field to the admin/SEMCMS_Categories.php?pid=1&lgid=1 URI. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18741 An XSS issue was discovered in SEMCMS 3.4 via admin/SEMCMS_Download.php?lgid=1 during editing. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18740 An XSS issue was discovered in SEMCMS 3.4 via the first input field to the admin/SEMCMS_Link.php?lgid=1 URI. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18739 An XSS issue was discovered in SEMCMS 3.4 via the admin/SEMCMS_Products.php?lgid=1 Keywords field. sem-cms · semcms 2018-10-29 medium4.8 CVE-2018-18738 An XSS issue was discovered in SEMCMS 3.4 via the admin/SEMCMS_Categories.php?pid=1&lgid=1 category_key parameter. sem-cms · semcms 2018-10-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.