NetSight

Security Dashboard

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

Reset
553 matching advisories · page 10 of 19Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2021-33352 An issue 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 a phar file upload in the t… wyomind · help_desk 2023-03-08 critical9.0 CVE-2021-33351 Cross Site Scripting Vulnerability in Wyomind Help Desk Magento 2 extension v.1.3.6 and before and fixed in v.1.3.7 allows attackers to escalte privileges via … wyomind · help_desk 2023-03-08 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 medium4.9 CVE-2023-23617 DoS vulnerability in MaliciousCode filter 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 medium4.2 CVE-2021-21395 Magneto LTS (Long Term Support) is a community developed alternative to the Magento CE official releases. composer · openmage/magento-lts 2023-01-26 medium6.1 CVE-2022-36433 The blog-post creation functionality in the Amasty Blog Pro 2.10.3 plugin for Magento 2 allows injection of JavaScript code in the short_content and full_conte… amasty · amasty_blog_pro 2022-11-29 medium5.4 CVE-2022-35501 Stored Cross-site Scripting (XSS) exists in the Amasty Blog Pro 2.10.3 and 2.10.4 plugin for Magento 2 because of the duplicate post function. amasty · blog_pro 2022-11-23 medium5.4 CVE-2022-36432 The Preview functionality in the Amasty Blog Pro 2.10.3 plugin for Magento 2 uses eval unsafely. amasty · blog_pro 2022-11-17 high8.8 CVE-2022-42344 Magento Improper input validation vulnerability composer · magento/community-edition 2022-10-20 critical10.0 CVE-2022-35698 Magento Open Source allows Stored Cross-Site Scripting (Stored XSS) composer · magento/community-edition, composer · magento/project-community-edition 2022-10-14 medium5.3 CVE-2022-35689 Magento Open Source allows Improper Access Control composer · magento/community-edition, composer · magento/project-community-edition 2022-10-14 medium5.3 CVE-2022-35692 Magento Open Source has Improper Access Control vulnerability composer · magento/community-edition, composer · magento/project-community-edition 2022-08-19 medium5.3 CVE-2022-34259 Magento Improper Access Control vulnerability composer · magento/community-edition 2022-08-16 medium5.5 CVE-2022-34258 Magento stored Cross-Site Scripting (XSS) vulnerability composer · magento/community-edition 2022-08-16 medium6.1 CVE-2022-34257 Magento stored Cross-Site Scripting (XSS) vulnerability composer · magento/community-edition 2022-08-16 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 critical9.1 CVE-2022-34253 Magento XML Injection vulnerability in the Widgets Module composer · magento/community-edition 2022-08-16 critical9.8 CVE-2022-24086 Magento improper input validation vulnerabilityExploited composer · magento/community-edition 2022-02-16 medium6.5 CVE-2021-39864 Magento Open Source allows Cross-Site Request Forgery (CSRF) composer · magento/community-edition, composer · magento/project-community-edition 2021-10-15 medium6.5 CVE-2021-28567 Magento versions 2.4.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are vulnerable to an Improper Authorization vulnerability in the custom… composer · magento/community-edition, composer · magento/project-community-edition 2021-09-08 low3.7 CVE-2021-28566 Magento versions 2.4.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are vulnerable to an Information Disclosure vulnerability when uploadin… composer · magento/community-edition 2021-09-08 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 critical9.1 CVE-2021-36042 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 in the… composer · magento/project-community-edition, composer · magento/community-edition 2021-09-01 critical9.1 CVE-2021-36041 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

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.