NetSight

Security Dashboard

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

Reset
106 matching advisories · page 2 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2020-36192 An issue was discovered in the Source Integration plugin before 2.4.1 for MantisBT. mantisbt · source_integration 2021-01-18 medium5.3 CVE-2020-28413 MantisBT SQL Injection via mc_project_get_users function composer · mantisbt/mantisbt 2020-12-30 medium4.8 CVE-2020-25830 MantisBT HTML Injection vulnerability composer · mantisbt/mantisbt 2020-09-30 medium4.3 CVE-2020-25781 MantisBT unauthorized users able to access private files composer · mantisbt/mantisbt 2020-09-30 medium4.8 CVE-2020-25288 MantisBT XXS where a Custom Field with a crafted Regular Expression property is used composer · mantisbt/mantisbt 2020-09-30 medium5.4 CVE-2020-16266 MantisBT XSS issue on the view_all_bug_page.php composer · mantisbt/mantisbt 2020-08-12 medium6.1 CVE-2019-15539 MantisBT XSS when uploading an attachment composer · mantisbt/mantisbt 2020-03-19 medium6.1 CVE-2020-8981 A cross-site scripting (XSS) vulnerability was discovered in the Source Integration plugin before 1.6.2 and 2.x before 2.3.1 for MantisBT. mantisbt · source_integration 2020-02-13 medium6.1 CVE-2009-2802 MantisBT 1.2.x before 1.2.2 insecurely handles attachments and MIME types. mantisbt · mantisbt 2019-11-09 medium4.3 CVE-2013-1811 An access control issue in MantisBT before 1.2.13 allows users with "Reporter" permissions to change any issue to "New". mantisbt · mantisbt, debian · debian_linux 2019-11-07 medium5.4 CVE-2013-1934 A cross-site scripting (XSS) vulnerability in the configuration report page (adm_config_report.php) in MantisBT 1.2.0rc1 before 1.2.14 allows remote authentica… mantisbt · mantisbt, debian · debian_linux 2019-10-31 medium5.4 CVE-2013-1932 A cross-site scripting (XSS) vulnerability in the configuration report page (adm_config_report.php) in MantisBT 1.2.13 allows remote authenticated users to inj… mantisbt · mantisbt 2019-10-31 medium6.1 CVE-2013-1931 A cross-site scripting (XSS) vulnerability in MantisBT 1.2.14 allows remote attackers to inject arbitrary web script or HTML via a version, related to deleting… mantisbt · mantisbt, fedoraproject · fedora 2019-10-31 medium4.3 CVE-2013-1930 MantisBT 1.2.12 before 1.2.15 allows authenticated users to by the workflow restriction and close issues. mantisbt · mantisbt, fedoraproject · fedora 2019-10-31 medium6.1 CVE-2018-16514 MantisBT cross-site scripting (XSS) vulnerability through crafted PATH_INFO composer · mantisbt/mantisbt 2019-06-20 medium6.5 CVE-2018-9839 An issue was discovered in MantisBT through 1.3.14, and 2.0.0. mantisbt · mantisbt 2019-06-06 medium5.4 CVE-2018-17783 MantisBT allows XSS via Edit Filter page composer · mantisbt/mantisbt 2018-10-30 medium5.4 CVE-2018-17782 MantisBT allows XSS via the Manage Filter page composer · mantisbt/mantisbt 2018-10-30 medium6.1 CVE-2018-16362 An issue was discovered in the Source Integration plugin before 1.5.9 and 2.x before 2.1.5 for MantisBT. mantisbt · source_integration 2018-09-02 medium6.1 CVE-2018-14504 MantisBT allows XSS on the Edit Filter page via crafted filter name composer · mantisbt/mantisbt 2018-08-03 medium6.1 CVE-2018-13055 MantisBT allows XSS via View Filters page composer · mantisbt/mantisbt 2018-08-03 medium5.3 CVE-2018-6526 view_all_bug_page.php in MantisBT 2.10.0-development before 2018-02-02 allows remote attackers to discover the full path via an invalid filter parameter, relat… mantisbt · mantisbt 2018-02-02 medium6.1 CVE-2015-2046 Cross-site scripting (XSS) vulnerability in MantisBT 1.2.13 and later before 1.2.20. mantisbt · mantisbt 2017-08-28 medium6.5 CVE-2014-9701 Cross-site scripting (XSS) vulnerability in MantisBT before 1.2.19 and 1.3.x before 1.3.0-beta.2 allows remote attackers to inject arbitrary web script or HTML… mantisbt · mantisbt 2017-08-09 medium4.9 CVE-2017-12419 If, after successful installation of MantisBT through 2.5.2 on MySQL/MariaDB, the administrator does not remove the 'admin' directory (as recommended in the "P… mantisbt · mantisbt 2017-08-05 medium6.1 CVE-2017-12062 MantisBT vulnerable to XSS via unsanitized filter field in manage_user_page.php composer · mantisbt/mantisbt 2017-08-01 medium6.1 CVE-2017-12061 MantisBT XSS allows unsanitized input via admin/install.php composer · mantisbt/mantisbt 2017-08-01 medium5.3 CVE-2015-5059 The "Project Documentation" feature in MantisBT 1.2.19 and earlier, when the threshold to access files ($g_view_proj_doc_threshold) is set to ANYBODY, allows r… mantisbt · mantisbt 2017-08-01 medium6.5 CVE-2017-7620 MantisBT vulnerable to CSRF and Open Redirect attacks composer · mantisbt/mantisbt 2017-05-21 medium6.1 CVE-2017-7897 MantisBT XSS via my_view_page.php and view_user_page.php composer · mantisbt/mantisbt 2017-04-18

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.