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 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2025-60454 A stored Cross-Site Scripting (XSS) vulnerability has been discovered in MetInfo CMS version 8.0. metinfo · metinfo 2025-10-03 medium6.1 CVE-2025-60453 A stored Cross-Site Scripting (XSS) vulnerability has been discovered in MetInfo CMS version 8.0. metinfo · metinfo 2025-10-03 medium6.1 CVE-2025-60452 A stored Cross-Site Scripting (XSS) vulnerability has been discovered in MetInfo CMS version 8.0. metinfo · metinfo 2025-10-03 medium6.1 CVE-2025-60451 A stored Cross-Site Scripting (XSS) vulnerability has been discovered in MetInfo CMS version 8.0. metinfo · metinfo 2025-10-03 medium6.1 CVE-2025-60450 A stored Cross-Site Scripting (XSS) vulnerability has been discovered in MetInfo CMS version 8.0. metinfo · metinfo 2025-10-03 medium5.4 CVE-2020-20600 MetInfo 7.0 beta contains a stored cross-site scripting (XSS) vulnerability in the $name parameter of admin/?n=column&c=index&a=doAddColumn. metinfo · metinfo 2021-12-22 medium6.1 CVE-2020-21517 Cross Site Scripting (XSS) vulnerability in MetInfo 7.0.0 via the gourl parameter in login.php. metinfo · metinfo 2021-06-21 medium6.5 CVE-2017-12790 Metinfo 5.3.18 is affected by: Cross Site Request Forgery (CSRF). metinfo · metinfo 2019-05-09 medium6.1 CVE-2017-12788 Multiple cross-site scripting (XSS) vulnerabilities in admin/index.php in Metinfo 5.3.18 allows remote attackers to inject arbitrary web script or HTML via the… metinfo · metinfo 2019-05-09 medium6.1 CVE-2018-20486 MetInfo 6.x through 6.1.3 has XSS via the /admin/login/login_check.php url_array[] parameter. metinfo · metinfo 2018-12-26 medium6.1 CVE-2018-19836 In Metinfo 6.1.3, include/interface/applogin.php allows setting arbitrary HTTP headers (including the Cookie header), and common.inc.php allows registering var… metinfo · metinfo 2018-12-03 medium6.1 CVE-2018-19835 Metinfo 6.1.3 has reflected XSS via the admin/column/move.php lang_columnerr4 parameter. metinfo · metinfo 2018-12-03 medium6.1 CVE-2018-19051 MetInfo 6.1.3 has XSS via the admin/index.php?a=dogetpassword abt_type parameter. metinfo · metinfo 2018-11-07 medium6.1 CVE-2018-19050 MetInfo 6.1.3 has XSS via the admin/index.php?a=dogetpassword langset parameter. metinfo · metinfo 2018-11-07 medium5.4 CVE-2018-18374 XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter. metinfo · metinfo 2018-10-16 medium6.1 CVE-2018-18296 MetInfo 6.1.2 has XSS via the /admin/index.php bigclass parameter in an n=column&a=doadd action. metinfo · metinfo 2018-10-15 medium4.9 CVE-2018-17129 MetInfo 6.1.0 has SQL injection in doexport() in app/system/feedback/admin/feedback_admin.class.php via the class1 field. metinfo · metinfo 2018-09-17 medium4.8 CVE-2018-14419 MetInfo 6.0.0 allows XSS via a modified name of the navigation bar on the home page. metinfo · metinfo 2018-07-20 medium6.5 CVE-2018-12530 An issue was discovered in MetInfo 6.0.0. metinfo · metinfo 2018-06-18 medium6.1 CVE-2018-9985 The front page of MetInfo 6.0 allows XSS by sending a feedback message to an administrator. metinfo · metinfo 2018-04-10 medium6.1 CVE-2018-9928 Cross-site scripting (XSS) vulnerability in save.php in MetInfo 6.0 allows remote attackers to inject arbitrary web script or HTML via the webname or weburl pa… metinfo · metinfo 2018-04-10 medium6.1 CVE-2018-7721 Cross Site Scripting (XSS) exists in MetInfo 6.0.0 via /feedback/index.php because app/system/feedback/web/feedback.class.php mishandles input data. metinfo · metinfo 2018-03-07 medium5.3 CVE-2017-14513 Directory traversal vulnerability in MetInfo 5.3.17 allows remote attackers to read information from any ini format file via the f_filename parameter in a fing… metinfo · metinfo 2017-09-17 medium6.1 CVE-2017-11718 There is URL Redirector Abuse in MetInfo through 5.3.17 via the gourl parameter to member/login.php. metinfo_project · metinfo 2017-07-28 medium6.1 CVE-2017-11716 MetInfo through 5.3.17 allows stored XSS via HTML Edit Mode. metinfo_project · metinfo 2017-07-28 medium6.1 CVE-2017-9764 Cross-site scripting (XSS) vulnerability in MetInfo 5.3.17 allows remote attackers to inject arbitrary web script or HTML via the Client-IP or X-Forwarded-For … metinfo · metinfo 2017-07-19 medium5.4 CVE-2017-6878 Cross-site scripting (XSS) vulnerability in MetInfo 5.3.15 allows remote authenticated users to inject arbitrary web script or HTML via the name_2 parameter to… metinfo · metinfo 2017-03-27 medium4.3 CVE-2010-4976 Cross-site scripting (XSS) vulnerability in search/search.php in MetInfo 3.0 allows remote attackers to inject arbitrary web script or HTML via the searchword … metinfo · metinfo 2011-11-01

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.