NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 25 of 60Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2011-4906 Tiny browser in TinyMCE 3.0 editor in Joomla! tiny · tinybrowser 2020-02-12 critical9.1 CVE-2011-1151 Joomla! joomla · joomla\! 2020-02-05 medium5.3 CVE-2011-4912 Joomla! joomla · joomla\! 2020-02-04 high7.5 CVE-2011-4937 Joomla! joomla · joomla\! 2020-02-04 high7.5 CVE-2011-3629 Joomla! joomla · joomla\! 2020-02-04 medium6.5 CVE-2020-5182 The J-BusinessDirectory extension before 5.2.9 for Joomla! cmsjunkie · j-businessdirectory 2020-02-03 medium6.1 CVE-2020-8421 An issue was discovered in Joomla! joomla · joomla\! 2020-01-28 high8.8 CVE-2020-8420 An issue was discovered in Joomla! joomla · joomla\! 2020-01-28 high8.8 CVE-2020-8419 An issue was discovered in Joomla! joomla · joomla\! 2020-01-28 medium5.4 CVE-2011-3595 Multiple Cross-site Scripting (XSS) vulnerabilities exist in Joomla! joomla · joomla\! 2020-01-22 medium5.3 CVE-2011-4907 Joomla! joomla · joomla\! 2020-01-15 high7.5 CVE-2012-1563 Joomla! joomla · joomla\! 2020-01-15 high7.5 CVE-2012-1562 Joomla! joomla · joomla\! 2020-01-15 high8.8 CVE-2013-3932 SQL injection vulnerability in the Jomres (com_jomres) component before 7.3.1 for Joomla! jomres · jomres 2020-01-02 medium5.4 CVE-2013-3931 Cross-site scripting (XSS) vulnerability in the Jomres (com_jomres) component before 7.3.1 for Joomla! jomres · jomres 2020-01-02 critical9.8 CVE-2019-17527 dataForDepandantField in models/custormfields.php in the JS JOBS FREE extension before 1.2.7 for Joomla! joomsky · js_jobs 2019-12-19 critical9.8 CVE-2019-19846 In Joomla! joomla · joomla\! 2019-12-18 medium5.3 CVE-2019-19845 In Joomla! joomla · joomla\! 2019-12-18 critical9.8 CVE-2019-19634 class.upload.php in verot.net omits .pht from the set of dangerous file extensions composer · verot/class.upload.php 2019-12-17 critical9.8 CVE-2019-19576 Remote code execution in verot/class.upload.php composer · verot/class.upload.php 2019-12-04 medium5.3 CVE-2013-6879 The Mijosoft MijoSearch component 2.0.1 and earlier for Joomla! miwisoft · mijosearch 2019-11-22 medium6.1 CVE-2013-6878 Cross-site scripting (XSS) vulnerability in the Mijosoft MijoSearch component 2.0.4 and earlier for Joomla! miwisoft · mijosearch 2019-11-22 high8.8 CVE-2014-1214 views/upload.php in the ProJoom Smart Flash Header (NovaSFH) component 3.0.2 and earlier for Joomla! projoom · smart_flash_header 2019-11-13 medium5.3 CVE-2019-18674 An issue was discovered in Joomla! joomla · joomla\! 2019-11-06 high8.8 CVE-2019-18650 An issue was discovered in Joomla! joomla · joomla\! 2019-11-06 medium6.1 CVE-2018-10727 Reflected Cross-Site Scripting (XSS) vulnerability in the fabrik_referrer hidden field in the Fabrikar Fabrik component through v3.8.1 for Joomla! fabrikar · fabrik 2019-10-29 critical9.8 CVE-2019-17399 The Shack Forms Pro extension before 4.0.32 for Joomla! joomlashack · shack_forms_pro 2019-10-09 medium6.1 CVE-2019-16725 Joomla! XSS in Default Templates composer · joomla/joomla-cms 2019-09-24 high8.8 CVE-2016-10960 The wsecure plugin before 2.4 for WordPress has remote code execution via shell metacharacters in the wsecure-config.php publish parameter. joomlaserviceprovider · wsecure 2019-09-16 medium5.4 CVE-2019-15120 The Kunena extension before 5.1.14 for Joomla! kunena · kunena 2019-08-16

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.