NetSight

Security Dashboard

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

Reset
68 matching advisories · page 1 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.1 CVE-2026-119558 OpenCart through 4.1.0.4 contains a business logic vulnerability that allows logged-in customers to place unpaid full-price orders by clearing reward points af… OpenCart 22 days ago critical9.8 CVE-2026-85531 Improper verification of cryptographic signature vulnerability in Sipay Electronic Money and Payment Services Inc. OpenCart Virtual POS Module: from 43 days ago low3.5 CVE-2026-84438 A vulnerability was determined in OpenCart 4.1.0.3/4.1.0.4. 2026-09-02 low3.5 CVE-2026-84437 A vulnerability was found in OpenCart 4.1.0.3/4.1.0.4. 2026-09-02 critical9.1 CVE-2026-18412 OpenCart extensions are uploaded as zip files with .ocmod.zip extensions. 2026-08-10 high8.2 CVE-2017-20282 Joomla! soft-php · jcart_for_opencart 2026-06-19 medium5.3 CVE-2018-25336 jCart for OpenCart 2.3.0.2 contains a cross-site request forgery vulnerability that allows attackers to modify user account information without authentication. 2026-05-17 medium4.3 CVE-2021-47953 OpenCart 3.0.3.7 contains a cross-site request forgery vulnerability that allows attackers to change user passwords by sending crafted requests to the account/… 2026-05-10 medium5.3 CVE-2021-47946 OpenCart 3.0.3.6 contains a cross-site request forgery vulnerability in the /account/edit endpoint that allows unauthenticated attackers to modify victim accou… 2026-05-10 high8.2 CVE-2021-47928 Opencart TMD Vendor System 3.x contains a blind SQL injection vulnerability that allows unauthenticated attackers to extract database information by injecting … 2026-05-10 critical9.8 CVE-2021-47923 OpenCart 3.0.3.8 contains a session fixation vulnerability that allows attackers to hijack user sessions by injecting arbitrary values into the OCSESSID cookie. 2026-05-10 medium4.7 CVE-2026-5331 A vulnerability was determined in OpenCart 4.1.0.3. 2026-04-02 high8.2 CVE-2024-58341 OpenCart Core 4.0.2.3 contains a SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through… opencart · opencart 2026-03-25 medium4.7 CVE-2026-3714 A vulnerability has been found in OpenCart 4.0.2.3. opencart · opencart 2026-03-08 low3.7 CVE-2025-15116 A security flaw has been discovered in OpenCart up to 4.1.0.3. opencart · opencart 2025-12-28 medium6.1 CVE-2025-45893 OpenCart version 4.1.0.4 is vulnerable to a Stored Cross-Site Scripting (XSS) attack via SVG file uploads used in blog posts. opencart · opencart 2025-07-25 medium6.1 CVE-2025-45892 OpenCart version 4.1.0.4 is vulnerable to a Stored Cross-Site Scripting (XSS) attack via the blog editor. opencart · opencart 2025-07-25 medium4.7 CVE-2025-1749 HTML injection vulnerabilities in OpenCart versions prior to 4.1.0. opencart · opencart 2025-02-28 medium4.7 CVE-2025-1748 HTML injection vulnerabilities in OpenCart versions prior to 4.1.0. opencart · opencart 2025-02-28 medium4.7 CVE-2025-1747 HTML injection vulnerabilities in OpenCart versions prior to 4.1.0. opencart · opencart 2025-02-28 medium6.1 CVE-2025-1746 Cross-Site Scripting vulnerability in OpenCart versions prior to 4.1.0. opencart · opencart 2025-02-28 high7.3 CVE-2025-1117 A vulnerability, which was classified as critical, was found in CoinRemitter 0.0.1/0.0.2 on OpenCart. 2025-02-08 high7.3 CVE-2025-1116 A vulnerability, which was classified as critical, has been found in Dreamvention Live AJAX Search Free up to 1.0.6 on OpenCart. Dreamvention Live AJAX Search Free 2025-02-08 medium5.0 CVE-2025-0974 A vulnerability was determined in MaxD Lightning Module 4.43/4.44 on OpenCart. 2025-02-03 high7.3 CVE-2025-0841 A vulnerability has been found in Aridius XYZ up to 20240927 on OpenCart and classified as critical. 2025-01-29 medium5.6 CVE-2025-0580 A vulnerability was found in Shiprocket Module 3 on OpenCart. 2025-01-20 high7.3 CVE-2025-0579 A vulnerability was found in Shiprocket Module 3/4 on OpenCart. 2025-01-20 high7.3 CVE-2025-0460 A vulnerability, which was classified as critical, was found in Blog Botz for Journal Theme 1.0 on OpenCart. 2025-01-14 high7.1 CVE-2025-22335 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in rajib.dewan Opencart Product in WP opencart-product-in-wp… WP: from n/a through 2025-01-07 medium4.1 CVE-2025-0214 A vulnerability was found in TMD Custom Header Menu 4.0.0.1 on OpenCart. 2025-01-04

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.