NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 30 of 60Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2018-5970 SQL Injection exists in the JGive 2.0.9 component for Joomla! techjoomla · jgive 2018-02-17 medium5.4 CVE-2015-3619 Cross-site scripting (XSS) vulnerability in assets/js/vm2admin.js in the VirtueMart component before 3.0.8 for Joomla! virtuemart · virtuemart 2018-02-06 high7.5 CVE-2018-6610 Information Leakage exists in the jLike 1.0 component for Joomla! jlike_project · jlike 2018-02-05 critical9.8 CVE-2018-6609 SQL Injection exists in the JSP Tickets 1.1 component for Joomla! jsp_tickets_project · jsp_tickets 2018-02-05 critical9.8 CVE-2018-6605 SQL Injection exists in the Zh BaiduMap 3.0.0.1 component for Joomla! zh_baidumap_project · zh_baidumap 2018-02-05 critical9.8 CVE-2018-6604 SQL Injection exists in the Zh YandexMap 6.2.1.0 component for Joomla! zh_yandexmap_project · zh_yandexmap 2018-02-05 critical9.8 CVE-2018-6582 SQL Injection exists in the Zh GoogleMap 8.4.0.0 component for Joomla! zh_googlemap_project · zh_googlemap 2018-02-05 critical9.8 CVE-2018-6581 SQL Injection exists in the JMS Music 1.1.1 component for Joomla! joommasters · jms_music 2018-02-02 critical9.8 CVE-2018-6580 Arbitrary file upload exists in the Jimtawl 2.1.6 and 2.2.5 component for Joomla! janguo · jimtawl 2018-02-02 critical9.8 CVE-2018-6579 SQL Injection exists in the JEXTN Reverse Auction 3.1.0 component for Joomla! jextn · reverse_auction 2018-02-02 critical9.8 CVE-2018-6578 SQL Injection exists in the JE PayperVideo 3.0.0 component for Joomla! jextn · je_paypervideo 2018-02-02 critical9.8 CVE-2018-6577 SQL Injection exists in the JEXTN Membership 3.1.0 component for Joomla! jextn · membership 2018-02-02 critical9.8 CVE-2018-6575 SQL Injection exists in the JEXTN Classified 1.0.0 component for Joomla! jextn · classified 2018-02-02 medium6.1 CVE-2018-6380 In Joomla! joomla · joomla\! 2018-01-30 medium6.1 CVE-2018-6379 In Joomla! joomla · joomla\! 2018-01-30 medium6.1 CVE-2018-6377 In Joomla! joomla · joomla\! 2018-01-30 critical9.8 CVE-2018-6376 In Joomla! joomla · joomla\! 2018-01-30 critical9.8 CVE-2018-6398 SQL Injection exists in the CP Event Calendar 3.0.1 component for Joomla! joomlacalendars · event_calendar 2018-01-30 high7.5 CVE-2018-6397 Directory Traversal exists in the Picture Calendar 3.1.4 component for Joomla! joomlacalendars · picture_calendar 2018-01-30 critical9.8 CVE-2018-6395 SQL Injection exists in the Visual Calendar 3.1.3 component for Joomla! joomlacalendars · visual_calendar 2018-01-30 high7.5 CVE-2018-6008 Arbitrary File Download exists in the Jtag Members Directory 5.3.7 component for Joomla! joomlatag · jtag_members_directory 2018-01-29 high8.8 CVE-2018-6007 CSRF exists in the JS Support Ticket 1.1.0 component for Joomla! joomsky · js_support_ticket 2018-01-29 critical9.8 CVE-2018-5985 SQL Injection exists in the LiveCRM SaaS Cloud 1.0 component for Joomla! livecrm · livecrm_saas_cloud 2018-01-24 critical9.8 CVE-2018-5984 SQL Injection exists in the Tumder (An Arcade Games Platform) 2.1 component for Joomla! tumder_project · tumder 2018-01-24 critical9.8 CVE-2018-5696 The iJoomla com_adagency plugin 6.0.9 for Joomla! ijoomla · ad_agency 2018-01-14 medium5.4 CVE-2018-5263 The StackIdeas EasyDiscuss (aka com_easydiscuss) extension before 4.0.21 for Joomla! stackideas · easydiscuss 2018-01-08 medium6.1 CVE-2015-7324 Multiple cross-site scripting (XSS) vulnerabilities in helpers/comment.php in the StackIdeas Komento (com_komento) component before 2.0.5 for Joomla! stackideas · komento 2017-12-27 critical9.8 CVE-2017-17875 The JEXTN FAQ Pro extension 4.0.0 for Joomla! jextn · jextn_faq_pro 2017-12-27 critical9.8 CVE-2017-17872 The JEXTN Video Gallery extension 3.0.5 for Joomla! jextn · jextn_video_gallery 2017-12-27 critical9.8 CVE-2017-17871 The "JEXTN Question And Answer" extension 3.1.0 for Joomla! jextn · jextn_question_and_answer 2017-12-27

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.