NetSight

Security Dashboard

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

Reset
301 matching advisories · page 1 of 11Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.6 CVE-2026-129957 PrestaShop before 8.2.9 and 9.0.0 before 9.2.1 contains a path traversal vulnerability in back-office theme and module archive import that allows authenticated… PrestaShop · PrestaShop 5 days ago high8.6 CVE-2026-71519 PrestaShop before 8.2.9 and 9.2.1 contains a broken access control vulnerability that allows an authenticated Webservice API key holder to read and modify cust… PrestaShop · PrestaShop 8 days ago high8.6 CVE-2026-71531 PrestaShop before 8.2.9 and 9.2.1 contains an authorization flaw in the Webservice API that allows an attacker holding a key restricted to one shop to act on d… PrestaShop · PrestaShop 8 days ago medium5.4 CVE-2026-124916 PrestaShop contains an authenticated PHP code injection vulnerability in the back-office Performance debug-mode configuration. PrestaShop · PrestaShop 12 days ago critical9.8 CVE-2026-86405 Improper verification of cryptographic signature vulnerability in Sipay Electronic Money and Payment Services Inc. PrestaShop Virtual POS Module: from 43 days ago critical9.3 CVE-2026-85520 Google Merchant Center Feed (gmfeed) module for PrestaShop is vulnerable to unauthenticated arbitrary file write in the feed.php endpoint. 53 days ago medium4.3 CVE-2026-92810 PrestaShop blockwishlist through 3.0.2 fails to validate wishlist ownership in the getUrlByIdWishListAction method, allowing authenticated customers to retriev… PrestaShop blockwishlist 2026-09-16 medium5.3 CVE-2026-92809 PrestaShop psgdpr versions through 1.4.3 fail to validate that GDPR consent log entries are attributed to the authenticated customer. PrestaShop · psgdpr 2026-09-16 high8.6 CVE-2026-7848 Alior Bank PrestaShop module "raty" for commercial partners is vulnerable to SQL Injection in the "hookActionObjectProductUpdateBefore", "hookActionObjectCateg… 2026-09-14 high8.6 CVE-2026-15600 Alior Bank PrestaShop module "raty" for commercial partners is vulnerable to SQL Injection in the toggleCategoryPromotionAction method. 2026-09-14 critical GHSA-4mv4-f8rv-6734 Malicious code in gulp-prestashop (npm)Malware npm · gulp-prestashop 2026-09-13 medium6.9 CVE-2026-84186 Vulnerability involving incorrect access control in the Tools::getRemoteAddr() function in PrestaShop, which allows the client’s IP address to be spoofed via t… 2026-09-07 medium5.4 CVE-2026-38725 xipblog module v2.0.1 and before for PrestaShop allows unauthenticated remote attackers to inject arbitrary JavaScript via the name and content parameters in a… 2026-08-28 high8.8 CVE-2026-50986 PrestaShop module, totadministrativemandate <1.8.1 is vulnerable to Cross Site Request Forgery (CSRF). PrestaShop module, totadministrativemandate 2026-07-31 medium4.5 CVE-2026-14846 In version 8.2.1 of PrestaShop, there is a vulnerability relating to the incorrect sanitisation of elements, caused by inadequate validation of the ‘Alias’ par… 2026-07-13 critical10.0 CVE-2026-54159 prestashop/ps_facetedsearch: PHP Object Injection in faceted search cache allows unauthenticated RCE composer · prestashop/ps_facetedsearch 2026-07-10 high7.5 CVE-2026-39079 An issue in prestashop upsshipping all versions through at least 2.4.0 allows a remote attacker to obtain sensitive information via the /modules/upsshipping/lo… 2026-05-18 critical9.3 CVE-2026-44212 PrestaShop has a stored XSS executable in customer service view composer · prestashop/prestashop 2026-05-08 low2.7 GHSA-mqq7-wxx5-mp8h ps_checkout allows unauthorized method invocation through unvalidated parameter composer · prestashop/ps_checkout 2026-04-30 high7.6 CVE-2026-33673 PrestaShop has multiple stored XSS vulnerabilities via unprotected Template variables composer · prestashop/prestashop 2026-03-25 low2.0 CVE-2026-33674 PrestaShop is an open source e-commerce web application. composer · prestashop/prestashop 2026-03-25 critical9.8 CVE-2025-69633 A SQL Injection vulnerability in the Advanced Popup Creator (advancedpopupcreator) module for PrestaShop 1.1.26 through 1.2.6 (Fixed in version 1.2.7) allows r… 2026-02-13 medium5.3 CVE-2026-25597 PrestaShop affected by time based enumeration in FO login form composer · prestashop/prestashop 2026-02-03 high7.1 CVE-2025-62945 Cross-Site Request Forgery (CSRF) vulnerability in Eduard Pinuaga Linares Did Prestashop Display did-prestashop-display allows Stored XSS.This issue affects Di… Did Prestashop Display: from n/a through 2025-10-27 low3.8 CVE-2025-61924 PrestaShop Checkout is the PrestaShop official payment module in partnership with PayPal. composer · prestashop/ps_checkout 2025-10-16 medium4.1 CVE-2025-61923 PrestaShop Checkout is the PrestaShop official payment module in partnership with PayPal. composer · prestashop/ps_checkout 2025-10-16 critical9.1 CVE-2025-61922 PrestaShop Checkout is the PrestaShop official payment module in partnership with PayPal. composer · prestashop/ps_checkout 2025-10-16 medium4.2 CVE-2025-51586 An issue was discoverd in file controllers/admin/AdminLoginController.php in PrestaShop before 8.2.1 allowing attackers to gain sensitive information via the r… composer · prestashop/prestashop 2025-09-04 medium6.5 CVE-2025-25692 A PHAR deserialization vulnerability in the _getHeaders function of PrestaShop v8.2.0 allows attackers to execute arbitrary code via a crafted POST request. prestashop · prestashop 2025-07-30 medium6.5 CVE-2025-25691 A PHAR deserialization vulnerability in the component /themes/import of PrestaShop v8.2.0 allows attackers to execute arbitrary code via a crafted POST request. prestashop · prestashop 2025-07-30

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.