NetSight

Security Dashboard

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

Reset
181 matching advisories · page 4 of 7Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2023-41879 Magento LTS's guest order "protect code" can be brute-forced too easily composer · openmage/magento-lts 2023-09-11 high7.5 CVE-2023-38207 Magento Open Source allows XML Injection composer · magento/community-edition, composer · magento/project-community-edition 2023-08-09 high7.5 CVE-2023-22248 Magento Open Source affected by Improper Input Validation composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 high7.5 CVE-2023-22247 Magento Open Source allows XML Injection composer · magento/community-edition, composer · magento/project-community-edition 2023-03-27 high7.2 CVE-2021-41231 DataFlow upload remote code execution vulnerability composer · openmage/magento-lts 2023-01-27 high8.8 CVE-2021-41144 Fix for authenticated remote code execution through layout update composer · openmage/magento-lts 2023-01-27 high7.2 CVE-2021-41143 Fix for arbitrary file deletion in customer media allows for remote code execution composer · openmage/magento-lts 2023-01-27 high7.2 CVE-2021-39217 Fix for arbitrary command execution in custom layout update through blocks composer · openmage/magento-lts 2023-01-27 high8.8 CVE-2022-42344 Magento Improper input validation vulnerability composer · magento/community-edition 2022-10-20 high7.5 CVE-2022-34256 Magento Improper Authorization vulnerability composer · magento/community-edition 2022-08-16 high8.8 CVE-2022-34255 Magento Improper Access Control vulnerability composer · magento/community-edition 2022-08-16 high8.5 CVE-2022-34254 Magento Path Traversal vulnerability composer · magento/community-edition 2022-08-16 high7.5 CVE-2021-36044 Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an improper input validation vulnerability. composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 high8.0 CVE-2021-36043 Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by a blind SSRF vulnerability in the bundled dotmail… composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 high8.3 CVE-2021-36032 Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an improper input validation vulnerability. composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 high7.2 CVE-2021-36031 Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by a Path Traversal vulnerability via the `theme[pre… composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 high7.5 CVE-2021-36030 Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an improper input validation vulnerability during… composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 high8.2 CVE-2021-36020 Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an XML Injection vulnerability in the 'City' fiel… composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 high7.2 CVE-2021-32759 OpenMage magento-lts is an alternative to the Magento CE official releases. composer · openmage/magento-lts 2021-08-27 high7.2 CVE-2021-32758 OpenMage Magento LTS is an alternative to the Magento CE official releases. composer · openmage/magento-lts 2021-08-27 high7.5 CVE-2021-28583 Magento versions 2.4.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are affected by a Violation of Secure Design Principles vulnerability i… composer · magento/community-edition, composer · magento/project-community-edition 2021-06-28 high8.1 CVE-2021-21030 Magento versions 2.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are vulnerable to a stored cross-site scripting (XSS) in the customer addr… composer · magento/community-edition, composer · magento/project-community-edition 2021-02-11 high8.0 CVE-2021-21015 Magento versions 2.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are vulnerable to an OS command injection via the customer attribute save … composer · magento/community-edition 2021-02-11 high8.7 CVE-2020-26295 OpenMage is a community-driven alternative to Magento CE. openmage · openmage 2021-01-21 high8.7 CVE-2020-26285 OpenMage is a community-driven alternative to Magento CE. openmage · openmage 2021-01-21 high8.7 CVE-2020-26252 OpenMage is a community-driven alternative to Magento CE. openmage · openmage 2021-01-20 high8.1 CVE-2021-21013 Magento versions 2.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are vulnerable to an insecure direct object vulnerability (IDOR) in the cu… adobe · magento 2021-01-13 high7.1 CVE-2020-24400 Magento versions 2.4.0 and 2.3.5 (and earlier) are affected by an SQL Injection vulnerability that could lead to sensitive information disclosure. composer · magento/community-edition 2020-11-09 high8.0 CVE-2020-15244 In Magento (rubygems openmage/magento-lts package) before versions 19.4.8 and 20.0.4, an admin user can generate soap credentials that can be used to trigger R… composer · openmage/magento-lts 2020-10-21 high8.0 CVE-2020-15151 Observable Timing Discrepancy in OpenMage LTS composer · openmage/magento-lts 2020-08-19

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.