NetSight

Security Dashboard

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

Reset
20 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2025-25686 semcms <=5.0 is vulnerable to SQL Injection in SEMCMS_Fuction.php. sem-cms · semcms 2025-03-27 critical9.8 CVE-2024-46103 SEMCMS 4.8 is vulnerable to SQL Injection via SEMCMS_Main.php. sem-cms · semcms 2024-09-20 critical9.8 CVE-2024-30938 SQL Injection vulnerability in SEMCMS v.4.8 allows a remote attacker to obtain sensitive information via the ID parameter in the SEMCMS_User.php component. sem-cms · semcms 2024-04-19 critical9.8 CVE-2024-31012 An issue was discovered in SEMCMS v.4.8, allows remote attackers to execute arbitrary code, escalate privileges, and obtain sensitive information via the uploa… sem-cms · semcms 2024-04-03 critical9.8 CVE-2024-25422 SQL Injection vulnerability in SEMCMS v.4.8 allows a remote attacker to execute arbitrary code and obtain sensitive information via the SEMCMS_Menu.php compone… sem-cms · semcms 2024-02-28 critical9.8 CVE-2023-50563 Semcms v4.8 was discovered to contain a SQL injection vulnerability via the AID parameter at SEMCMS_Function.php. sem-cms · semcms 2023-12-14 critical9.8 CVE-2023-37647 SEMCMS v1.5 was discovered to contain a SQL injection vulnerability via the id parameter at /Ant_Suxin.php. sem-cms · semcms 2023-07-31 critical9.8 CVE-2020-18432 File Upload vulnerability in SEMCMS PHP 3.7 allows remote attackers to upload arbitrary files and gain escalated privileges. sem-cms · semcms 2023-06-30 critical9.8 CVE-2023-31707 SEMCMS 1.5 is vulnerable to SQL Injection via Ant_Rponse.php. sem-cms · semcms 2023-05-19 critical9.8 CVE-2023-30090 Semcms Shop v4.2 was discovered to contain an arbitrary file uplaod vulnerability via the component SEMCMS_Upfile.php. sem-cms · semcms 2023-05-05 critical9.8 CVE-2021-38733 SEMCMS SHOP v 1.1 is vulnerable to SQL Injection via Ant_BlogCat.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38732 SEMCMS SHOP v 1.1 is vulnerable to SQL via Ant_Message.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38731 SEMCMS SHOP v 1.1 is vulnerable to SQL Injection via Ant_Zekou.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38730 SEMCMS SHOP v 1.1 is vulnerable to SQL Injection via Ant_Info.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38729 SEMCMS SHOP v 1.1 is vulnerable to SQL Injection via Ant_Plist.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38217 SEMCMS v 1.2 is vulnerable to SQL Injection via SEMCMS_User.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38737 SEMCMS v 1.1 is vulnerable to SQL Injection via Ant_Pro.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38736 SEMCMS Shop V 1.1 is vulnerable to SQL Injection via Ant_Global.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2021-38734 SEMCMS SHOP v 1.1 is vulnerable to SQL Injection via Ant_Menu.php. sem-cms · semcms 2022-10-28 critical9.8 CVE-2020-18078 A vulnerability in /include/web_check.php of SEMCMS v3.8 allows attackers to reset the Administrator account's password. sem-cms · semcms 2021-12-17

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.