NetSight

Security Dashboard

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

Reset
301 matching advisories · page 8 of 11Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2022-22897 A SQL injection vulnerability in the product_all_one_img and image_product parameters of the ApolloTheme AP PageBuilder component through 2.4.4 for PrestaShop … apollotheme · ap_pagebuilder 2022-08-29 critical9.8 CVE-2022-31181 PrestaShop eval injection possible if shop vulnerable to SQL injection composer · prestashop/prestashop 2022-07-29 critical9.8 CVE-2022-36408 Duplicate Advisory GHSA-hrgx-p36p-89q4 composer · prestashop/prestashop 2022-07-22 medium4.8 CVE-2020-21967 File upload vulnerability in the Catalog feature in Prestashop 1.7.6.7 allows remote attackers to run arbitrary code via the add new file page. prestashop · prestashop 2022-07-13 high8.1 CVE-2022-31101 prestashop/blockwishlist is a prestashop extension which adds a block containing the customer's wishlists. composer · prestashop/blockwishlist 2022-06-25 critical9.0 CVE-2022-21686 PrestaShop is an Open Source e-commerce platform. composer · prestashop/prestashop 2022-01-26 medium6.1 CVE-2012-20001 PrestaShop before 1.5.2 allows XSS via the "<object data='data:text/html" substring in the message field. composer · prestashop/prestashop 2021-12-21 high7.5 CVE-2021-43789 PrestaShop is an Open Source e-commerce web application. composer · prestashop/prestashop 2021-12-07 critical9.8 CVE-2021-40814 The Customer Photo Gallery addon before 2.9.4 for PrestaShop is vulnerable to SQL injection. mypresta · customer_photo_gallery 2021-09-08 critical9.8 CVE-2021-37538 Multiple SQL injection vulnerabilities in SmartDataSoft SmartBlog for PrestaShop before 4.06 allow a remote unauthenticated attacker to execute arbitrary SQL c… smartdatasoft · smartblog 2021-08-24 high7.5 CVE-2021-36748 A SQL Injection issue in the list controller of the Prestahome Blog (aka ph_simpleblog) module before 1.7.8 for Prestashop allows a remote attacker to extract … prestahome · blog 2021-08-20 medium4.6 CVE-2021-21418 ps_emailsubscription is a newsletter subscription module for the PrestaShop platform. composer · prestashop/ps_emailsubscription 2021-03-31 medium5.4 CVE-2021-21398 PrestaShop is a fully scalable open source e-commerce solution. prestashop · prestashop 2021-03-30 medium6.1 CVE-2021-21308 PrestaShop is a fully scalable open source e-commerce solution. prestashop · prestashop 2021-02-26 medium6.8 CVE-2021-21302 PrestaShop is a fully scalable open source e-commerce solution. prestashop · prestashop 2021-02-26 medium5.3 CVE-2020-16194 An Insecure Direct Object Reference (IDOR) vulnerability was found in Prestashop Opart devis < 4.0.2. store-opart · op\'art_devis 2021-02-04 critical9.8 CVE-2021-3110 The store system in PrestaShop 1.7.7.0 allows time-based boolean SQL injection via the module=productcomments controller=CommentGrade id_products[] parameter. prestashop · prestashop 2021-01-20 medium6.8 CVE-2020-26248 In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. composer · prestashop/productcomments 2020-12-03 high7.5 CVE-2020-26224 In PrestaShop before version 1.7.6.9 an attacker is able to list all the orders placed on the website without being logged by abusing the function that allows … prestashop · prestashop 2020-11-16 high8.7 CVE-2020-26225 In PrestaShop Product Comments before version 4.2.0, an attacker could inject malicious web code into the users' web browsers by creating a malicious link. composer · prestashop/productcomments 2020-11-16 high7.5 CVE-2020-9368 The Module Olea Gift On Order module through 5.0.8 for PrestaShop enables an unauthenticated user to read arbitrary files on the server via getfile.php?file=/.. oleacorner · olea_gift_on_order 2020-11-02 medium5.4 CVE-2020-15162 In PrestaShop from version 1.5.0.0 and before version 1.7.6.8, users are allowed to send compromised files. prestashop · prestashop 2020-09-24 critical9.8 CVE-2020-15160 PrestaShop from version 1.7.5.0 and before version 1.7.6.8 is vulnerable to a blind SQL Injection attack in the Catalog Product edition page with location para… prestashop · prestashop 2020-09-24 medium5.4 CVE-2020-15161 In PrestaShop from version 1.6.0.4 and before version 1.7.6.8 an attacker is able to inject javascript while using the contact form. prestashop · prestashop 2020-09-24 high8.0 CVE-2020-15178 In PrestaShop contactform module (prestashop/contactform) before version 4.3.0, an attacker is able to inject JavaScript while using the contact form. composer · prestashop/contactform 2020-09-15 medium6.5 CVE-2020-15102 In PrestaShop Dashboard Productions before version 2.1.0, there is improper authorization which enables an attacker to change the configuration. prestashop · dashboard_products 2020-07-21 high8.9 CVE-2020-4074 In PrestaShop from version 1.5.0.0 and before version 1.7.6.6, the authentication system is malformed and an attacker is able to forge requests and execute adm… prestashop · prestashop 2020-07-02 medium4.7 CVE-2020-15083 In PrestaShop from version 1.7.0.0 and before version 1.7.6.6, if a target sends a corrupted file, it leads to a reflected XSS. prestashop · prestashop 2020-07-02 high7.1 CVE-2020-15082 In PrestaShop from version 1.6.0.1 and before version 1.7.6.6, the dashboard allows rewriting all configuration variables. prestashop · prestashop 2020-07-02 medium5.3 CVE-2020-15081 In PrestaShop from version 1.5.0.0 and before 1.7.6.6, there is information exposure in the upload directory. prestashop · prestashop 2020-07-02

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.