NetSight

Security Dashboard

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

Reset
24 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.2 CVE-2017-20282 Joomla! soft-php · jcart_for_opencart 2026-06-19 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 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 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 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 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 high7.2 GHSA-j2v2-3784-vr44 Duplicate Advisory: openCart Server-Side Template Injection (SSTI) vulnerability composer · opencart/opencart 2024-12-18 high7.2 CVE-2024-36694 openCart Server-Side Template Injection (SSTI) vulnerability composer · opencart/opencart 2024-07-17 high6.6 CVE-2024-21519 Arbitrary File Creation in opencart composer · opencart/opencart 2024-06-22 high7.2 CVE-2024-21518 Zip slip in opencart composer · opencart/opencart 2024-06-22 high7.4 CVE-2024-21514 SQL injection in opencart composer · opencart/opencart 2024-06-22 high8.8 CVE-2023-47444 An issue discovered in OpenCart 4.0.0.0 to 4.0.2.3 allows authenticated backend users having common/security write privilege can write arbitrary untrusted data… opencart · opencart 2023-11-15 high8.1 CVE-2023-2315 OpenCart Path Traversal vulnerability composer · opencart/opencart 2023-09-27 high7.2 CVE-2020-20491 SQL injection vulnerability in OpenCart v.2.2.00 thru 3.0.3.2 allows a remote attacker to execute arbitrary code via the Fba plugin function in upload/admin/in… opencart · opencart 2023-06-20 high7.5 CVE-2020-15478 The Journal theme before 3.1.0 for OpenCart allows exposure of sensitive data via SQL errors. journal-theme · journal 2020-07-01 high8.8 CVE-2018-13067 OpenCart Cross-Site Request Forgery (CSRF) composer · opencart/opencart 2018-07-02 high8.0 CVE-2018-11494 OpenCart Path Traversal composer · opencart/opencart 2018-05-26 high8.1 CVE-2018-11231 In the Divido plugin for OpenCart, there is SQL injection. divido · divido 2018-05-23 high7.2 CVE-2016-10509 SQL injection vulnerability in the updateAmazonOrderTracking function in upload/admin/model/openbay/amazon.php in OpenCart before version 2.3.0.0 allows remote… opencart · opencart 2017-08-31 high7.5 CVE-2010-0956 SQL injection vulnerability in index.php in OpenCart 1.3.2 allows remote attackers to execute arbitrary SQL commands via the page parameter. opencart · opencart 2010-03-10 high7.5 CVE-2009-1027 SQL injection vulnerability in OpenCart 1.1.8 allows remote attackers to execute arbitrary SQL commands via the order parameter. opencart · opencart 2009-03-20

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.