NetSight

Security Dashboard

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

Reset
126 matching advisories · page 2 of 5Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2025-25800 SeaCMS 13.3 was discovered to contain an arbitrary file read vulnerability in the file_get_contents function at admin_safe_file.php. seacms · seacms 2025-02-26 medium6.0 CVE-2025-25799 SeaCMS 13.3 was discovered to contain an arbitrary file read vulnerability in the file_get_contents function at admin_safe.php. seacms · seacms 2025-02-26 medium5.1 CVE-2025-25797 SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component admin_smtp.php. seacms · seacms 2025-02-26 medium5.1 CVE-2025-25796 SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component admin_template.php. seacms · seacms 2025-02-26 medium5.1 CVE-2025-25794 SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component admin_ping.php. seacms · seacms 2025-02-26 medium5.1 CVE-2025-25793 SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component admin_notify.php. seacms · seacms 2025-02-26 medium4.4 CVE-2025-25792 SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the isopen parameter at admin_weixin.php. seacms · seacms 2025-02-26 critical9.8 CVE-2025-25521 Seacms <=13.3 is vulnerable to SQL Injection in admin_type_news.php. seacms · seacms 2025-02-25 critical9.8 CVE-2025-25520 Seacms <13.3 is vulnerable to SQL Injection in admin_pay.php. seacms · seacms 2025-02-25 critical9.8 CVE-2025-25519 Seacms <=13.3 is vulnerable to SQL Injection in admin_zyk.php. seacms · seacms 2025-02-25 critical9.8 CVE-2025-25517 Seacms <=13.3 is vulnerable to SQL Injection in admin_reslib.php. seacms · seacms 2025-02-25 critical9.8 CVE-2025-25516 Seacms <=13.3 is vulnerable to SQL Injection in admin_paylog.php. seacms · seacms 2025-02-25 high8.8 CVE-2025-25515 Seacms <=13.3 is vulnerable to SQL Injection in admin_collect.php that allows an authenticated attacker to exploit the database. seacms · seacms 2025-02-25 medium6.5 CVE-2025-25514 Seacms <=13.3 is vulnerable to SQL Injection in admin_collect_news.php. seacms · seacms 2025-02-25 critical9.8 CVE-2025-22974 SQL Injection vulnerability in SeaCMS v.13.2 and before allows a remote attacker to execute arbitrary code via the DoTranExecSql parameter in the phome.php com… seacms · seacms 2025-02-24 critical9.8 CVE-2025-25513 Seacms <=13.3 is vulnerable to SQL Injection in admin_members.php. seacms · seacms 2025-02-24 critical9.1 CVE-2024-54880 SeaCMS V13.1 is vulnerable to Incorrect Access Control. seacms · seacms 2025-01-06 critical9.1 CVE-2024-54879 SeaCMS V13.1 is vulnerable to Incorrect Access Control. seacms · seacms 2025-01-06 critical9.8 CVE-2024-55461 SeaCMS <=13.0 is vulnerable to command execution in phome.php via the function Ebak_RepPathFiletext(). seacms · seacms 2024-12-18 high8.8 CVE-2024-50808 SeaCms 13.1 is vulnerable to code injection in the notification module of the member message notification module in the backend user module, due to unsafe hand… seacms · seacms 2024-11-08 critical9.8 CVE-2024-46640 SeaCMS 13.2 has a remote code execution vulnerability located in the file sql.class.chp. seacms · seacms 2024-09-20 critical9.8 CVE-2024-44721 SeaCMS v13.1 was discovered to a Server-Side Request Forgery (SSRF) via the url parameter at /admin_reslib.php. seacms · seacms 2024-09-09 high7.5 CVE-2024-44720 SeaCMS v13.1 was discovered to an arbitrary file read vulnerability via the component admin_safe.php. seacms · seacms 2024-09-09 critical9.8 CVE-2024-44921 SeaCMS v12.9 was discovered to contain a SQL injection vulnerability via the id parameter at /dmplayer/dmku/index.php?ac=del. seacms · seacms 2024-09-03 medium6.1 CVE-2024-44920 A cross-site scripting (XSS) vulnerability in the component admin_collect_news.php of SeaCMS v12.9 allows attackers to execute arbitrary web scripts or HTML vi… seacms · seacms 2024-09-03 medium6.1 CVE-2024-44683 Seacms v13 is vulnerable to Cross Site Scripting (XSS) via admin-video.php. seacms · seacms 2024-08-30 low3.5 CVE-2024-44918 A cross-site scripting (XSS) vulnerability in the component admin_datarelate.php of SeaCMS v12.9 allows attackers to execute arbitrary web scripts or HTML via … seacms · seacms 2024-08-30 high7.2 CVE-2024-44916 Vulnerability in admin_ip.php in Seacms v13.1, when action=set, allows attackers to control IP parameters that are written to the data/admin/ip.php file and co… seacms · seacms 2024-08-30 medium5.4 CVE-2024-44919 A cross-site scripting (XSS) vulnerability in the component admin_ads.php of SeaCMS v12.9 allows attackers to execute arbitrary web scripts or HTML via a craft… seacms · seacms 2024-08-29 critical9.8 CVE-2024-41444 SeaCMS v12.9 has a SQL injection vulnerability in the key parameter of /js/player/dmplayer/dmku/index.php?ac=so. seacms · seacms 2024-08-26

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.