NetSight

Security Dashboard

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

Reset
553 matching advisories · page 13 of 19Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2020-24408 Magento versions 2.4.0 and 2.3.5p1 (and earlier) are affected by a persistent XSS vulnerability that allows users to upload malicious JavaScript via the file u… composer · magento/community-edition 2020-10-16 high8.0 CVE-2020-15151 Observable Timing Discrepancy in OpenMage LTS composer · openmage/magento-lts 2020-08-19 high8.8 CVE-2020-13404 The ATOS/Sips (aka Atos-Magento) community module 3.0.0 to 3.0.5 for Magento allows command injection. quadra-informatique · atos\/sips 2020-08-05 medium6.5 CVE-2020-9692 Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have a security mitigation bypass vulnerability. composer · magento/community-edition 2020-07-29 critical9.6 CVE-2020-9691 Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have a dom-based cross-site scripting vulnerability. composer · magento/community-edition, composer · magento/project-community-edition 2020-07-29 medium4.2 CVE-2020-9690 Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have an observable timing discrepancy vulnerability. composer · magento/community-edition 2020-07-29 medium6.5 CVE-2020-9689 Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have a path traversal vulnerability. composer · magento/community-edition, composer · magento/project-community-edition 2020-07-29 medium6.1 CVE-2020-9665 Magento versions 1.14.4.5 and earlier, and 1.9.4.5 and earlier have a stored cross-site scripting vulnerability. composer · magento/core 2020-07-22 critical9.8 CVE-2020-9664 Magento versions 1.14.4.5 and earlier, and 1.9.4.5 and earlier have a php object injection vulnerability. composer · magento/core 2020-07-22 medium4.8 CVE-2020-13423 Form Builder 2.1.0 for Magento has multiple XSS issues that can be exploited against Magento 2 admin accounts via the Current_url or email field, or the User-A… form_builder_for_magento_2_project · form_builder_for_magento_2 2020-06-29 medium6.1 CVE-2020-12635 XSS exists in the WebForms Pro M2 extension before 2.9.17 for Magento 2 via the textarea field. mageme · webforms_pro_m2 2020-06-29 critical9.8 CVE-2020-9632 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a security mitigation bypass vulnerabilit… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9631 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a security mitigation bypass vulnerabilit… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9630 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a business logic error vulnerability. composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 high7.5 CVE-2020-9591 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a defense-in-depth security mitigation vu… composer · magento/community-edition, composer · magento/core 2020-06-26 high7.2 CVE-2020-9588 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have an observable timing discrepancy vulnerab… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 high7.5 CVE-2020-9587 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have an authorization bypass vulnerability. composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9585 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a defense-in-depth security mitigation vu… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 medium5.4 CVE-2020-9584 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a stored cross-site scripting vulnerabili… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9583 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a command injection vulnerability. composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9582 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a command injection vulnerability. composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 medium6.1 CVE-2020-9581 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a stored cross-site scripting vulnerabili… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9580 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a security mitigation bypass vulnerabilit… composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9579 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a security mitigation bypass vulnerabilit… composer · magento/community-edition, composer · magento/core 2020-06-26 critical9.8 CVE-2020-9578 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a command injection vulnerability. composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 medium6.1 CVE-2020-9577 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a stored cross-site scripting vulnerabili… composer · magento/core, composer · magento/community-edition, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2020-9576 Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a command injection vulnerability. composer · magento/community-edition, composer · magento/core, composer · magento/project-community-edition 2020-06-26 critical9.8 CVE-2014-1634 SQL Injection exists in Advanced Newsletter Magento extension before 2.3.5 via the /store/advancednewsletter/index/subscribeajax/an_category_id/ PATH_INFO. magento · advanced_newsletter 2020-03-09 high8.1 CVE-2020-8818 An issue was discovered in the CardGate Payments plugin through 2.0.30 for Magento 2. composer · cardgate/magento2 2020-02-25 high7.5 CVE-2012-6091 Zend_XmlRpc Class in Magento before 1.7.0.2 contains an information disclosure vulnerability. magentocommerce · magento 2020-02-13

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.