NetSight

Security Dashboard

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

Reset
553 matching advisories · page 9 of 19Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2023-38220 Magento Open Source allows Improper Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-10-13 high8.7 CVE-2023-38219 Magento Open Source allows Cross-Site Scripting (XSS) composer · magento/community-edition, composer · magento/project-community-edition 2023-10-13 high8.8 CVE-2023-38218 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-10-13 medium4.9 CVE-2023-26367 Magento Open Source has Improper Input Validation Vulnerability composer · magento/community-edition, composer · magento/project-community-edition 2023-10-13 medium6.8 CVE-2023-26366 Magento Open Source allows Server-Side Request Forgery (SSRF) composer · magento/community-edition, composer · magento/project-community-edition 2023-10-13 critical9.1 CVE-2022-24093 Magento Open Source affected by Improper Input Validation composer · magento/community-edition, composer · magento/project-community-edition 2023-09-12 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 critical9.1 CVE-2021-36036 Magento versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an improper access control vulnerability within Magento's … composer · magento/project-community-edition, composer · magento/community-edition 2023-09-06 critical9.1 CVE-2021-36023 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 Widgets Upd… composer · magento/project-community-edition, composer · magento/community-edition 2023-09-06 critical9.1 CVE-2021-36021 Magento 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 within the CMS … composer · magento/project-community-edition, composer · magento/community-edition 2023-09-06 medium6.5 CVE-2023-38209 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-08-09 critical9.1 CVE-2023-38208 Magento Open Source allows Improper Neutralization of Special Elements Used composer · magento/community-edition, composer · magento/project-community-edition 2023-08-09 high7.5 CVE-2023-38207 Magento Open Source allows XML Injection composer · magento/community-edition, composer · magento/project-community-edition 2023-08-09 critical9.1 CVE-2023-29297 Magento Open Source allows Improper Neutralization of Special Elements Used composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium4.3 CVE-2023-29296 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium4.3 CVE-2023-29295 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium4.3 CVE-2023-29294 Magento Open Source has Business Logic Errors Vulnerability composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 low2.7 CVE-2023-29293 Magento Open Source affected by Improper Input Validation composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium4.9 CVE-2023-29292 Magento Open Source allows Server-Side Request Forgery (SSRF) composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium4.9 CVE-2023-29291 Magento Open Source allows Server-Side Request Forgery (SSRF) composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium5.3 CVE-2023-29290 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium6.5 CVE-2023-29289 Magento Open Source allows XML Injection composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium4.3 CVE-2023-29288 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 medium5.3 CVE-2023-29287 Magento Open Source allows Information Exposure composer · magento/community-edition, composer · magento/project-community-edition 2023-06-15 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 medium4.3 CVE-2023-22251 Magento Open Source allows Incorrect Authorization composer · magento/community-edition, composer · magento/project-community-edition 2023-03-27 medium5.3 CVE-2023-22250 Magento Open Source allows Improper Access Control composer · magento/community-edition, composer · magento/project-community-edition 2023-03-27 medium4.8 CVE-2023-22249 Magento Open Source allows Cross-Site Scripting (XSS) composer · magento/community-edition 2023-03-27 high7.5 CVE-2023-22247 Magento Open Source allows XML Injection composer · magento/community-edition, composer · magento/project-community-edition 2023-03-27 critical9.8 CVE-2021-33353 Directory Traversal vulnerability in Wyomind Help Desk Magento 2 extension v.1.3.6 and before fixed in v.1.3.7 allows attacker to execute arbitrary code via th… wyomind · help_desk 2023-03-08

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.