NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 20 of 60Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2024-9941 The WPGYM - Wordpress Gym Management System plugin for WordPress is vulnerable to privilege escalation due to a missing capability check on the MJ_gmgt_add_sta… mojoomla · wordpress_gym_management_system 2024-11-23 medium5.4 CVE-2024-40746 A stored cross-site scripting (XSS) vulnerability in HikaShop Joomla Component < 5.1.1 allows remote attackers to execute arbitrary JavaScript in the web brows… hikashop · hikashop 2024-10-21 medium6.1 CVE-2024-40743 The stripImages and stripIframes methods didn't properly process inputs, leading to XSS vectors. joomla · joomla\! 2024-08-20 high7.5 CVE-2024-27187 Improper Access Controls allows backend users to overwrite their username when disallowed. joomla · joomla\! 2024-08-20 medium6.1 CVE-2024-27186 The mail template feature lacks an escaping mechanism, causing XSS vectors in multiple extensions. joomla · joomla\! 2024-08-20 critical9.1 CVE-2024-27185 The pagination class includes arbitrary parameters in links, leading to cache poisoning attack vectors. joomla · joomla\! 2024-08-20 medium6.1 CVE-2024-27184 Inadequate validation of URLs could result into an invalid check whether an redirect URL is internal or not.. joomla · joomla\! 2024-08-20 medium6.1 CVE-2024-27183 XSS vulnerability in DJ-HelpfulArticles component for Joomla. dj-extensions · dj-helpfularticles 2024-07-09 medium6.1 CVE-2024-26279 The wrapper extensions do not correctly validate inputs, leading to XSS vectors. joomla · joomla\! 2024-07-09 medium6.1 CVE-2024-26278 The Custom Fields component not correctly filter inputs, leading to a XSS vector. joomla · joomla\! 2024-07-09 medium6.1 CVE-2024-21731 Improper handling of input could lead to an XSS vector in the StringHelper::truncate method. joomla · joomla\! 2024-07-09 medium5.4 CVE-2024-21730 The fancyselect list field layout does not correctly escape inputs, leading to a self-XSS vector. joomla · joomla\! 2024-07-09 medium6.1 CVE-2024-21729 Inadequate input validation leads to XSS vulnerabilities in the accessiblemedia field. joomla · joomla\! 2024-07-09 medium6.1 CVE-2024-5737 Script afGdStream.php in AdmirorFrames Joomla! admiror-design-studio · admirorframes 2024-06-28 high7.5 CVE-2024-5736 Server Side Request Forgery (SSRF) vulnerability in AdmirorFrames Joomla! admiror-design-studio · admirorframes 2024-06-28 high7.5 CVE-2024-5735 Full Path Disclosure vulnerability in AdmirorFrames Joomla! admiror-design-studio · admirorframes 2024-06-28 medium5.3 CVE-2024-32788 Insertion of Sensitive Information into Log File vulnerability in Frédéric GILLES FG Joomla to WordPress.This issue affects FG Joomla to WordPress: from n/a th… FG Joomla to WordPress: from n/a 2024-04-24 medium6.5 CVE-2024-21726 Inadequate content filtering leads to XSS vulnerabilities in various components. joomla · joomla\! 2024-02-29 medium6.1 CVE-2024-21725 Inadequate escaping of mail addresses lead to XSS vulnerabilities in various components. joomla · joomla\! 2024-02-29 medium6.1 CVE-2024-21724 Inadequate input validation for media selection fields lead to XSS vulnerabilities in various extensions. joomla · joomla\! 2024-02-29 medium4.3 CVE-2024-21723 Inadequate parsing of URLs could result into an open redirect. joomla · joomla\! 2024-02-29 medium6.3 CVE-2024-21722 The MFA management features did not properly terminate existing user sessions when a user's MFA methods have been modified. joomla · joomla\! 2024-02-29 medium4.3 CVE-2024-24837 Cross-Site Request Forgery (CSRF) vulnerability in Frédéric GILLES FG PrestaShop to WooCommerce, Frédéric GILLES FG Drupal to WordPress, Frédéric GILLES FG Joo… FG PrestaShop to WooCommerce: from n/a, FG Drupal to WordPress: from n/a, FG Joomla to WordPress: from n/a 2024-02-21 medium6.1 CVE-2024-21727 XSS vulnerability in DP Calendar component for Joomla. digital-peak · dpcalendar 2024-02-15 critical9.8 CVE-2023-49708 SQLi vulnerability in Starshop component for Joomla. joomstar · starshop 2023-12-14 critical9.8 CVE-2023-49707 SQLi vulnerability in S5 Register module for Joomla. joomlart · s5_register 2023-12-14 medium6.1 CVE-2023-40659 A reflected XSS vulnerability was discovered in the Easy Quick Contact module for Joomla. joomboost · easy_quick_contact 2023-12-14 medium6.1 CVE-2023-40658 A reflected XSS vulnerability was discovered in the Clicky Analytics Dashboard module for Joomla. deconf · clicky_analytics_dashboard 2023-12-14 medium6.1 CVE-2023-40657 A reflected XSS vulnerability was discovered in the Joomdoc component for Joomla. artio · joomdoc 2023-12-14 medium6.1 CVE-2023-40656 A reflected XSS vulnerability was discovered in the Quickform component for Joomla. plasma-web · quickform 2023-12-14

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.