NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 27 of 60Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2019-7740 An issue was discovered in Joomla! joomla · joomla\! 2019-02-12 medium6.1 CVE-2019-7739 An issue was discovered in Joomla! joomla · joomla\! 2019-02-12 critical9.8 CVE-2016-1000271 Joomla extension DT Register version before 3.1.12 (Joomla 3.x) / 2.8.18 (Joomla 2.5) contains an SQL injection in "/index.php?controller=calendar&format=raw&c… dthdevelopment · dt_register 2019-02-04 medium6.1 CVE-2019-6264 An issue was discovered in Joomla! joomla · joomla\! 2019-01-16 medium4.8 CVE-2019-6263 An issue was discovered in Joomla! joomla · joomla\! 2019-01-16 medium5.4 CVE-2019-6262 An issue was discovered in Joomla! joomla · joomla\! 2019-01-16 medium6.1 CVE-2019-6261 An issue was discovered in Joomla! joomla · joomla\! 2019-01-16 medium4.3 CVE-2018-17859 An issue was discovered in Joomla! joomla · joomla\! 2018-10-09 high8.8 CVE-2018-17858 An issue was discovered in Joomla! joomla · joomla\! 2018-10-09 medium4.3 CVE-2018-17857 An issue was discovered in Joomla! joomla · joomla\! 2018-10-09 high7.2 CVE-2018-17856 Joomla RCE Vulnerability composer · joomla/framework 2018-10-09 high8.8 CVE-2018-17855 An issue was discovered in Joomla! joomla · joomla\! 2018-10-09 critical9.8 CVE-2018-17397 SQL Injection exists in the AlphaIndex Dictionaries 1.0 component for Joomla! multiplanet · alphaindex_dictionaries 2018-09-28 critical9.8 CVE-2018-17394 SQL Injection exists in the Timetable Schedule 3.6.8 component for Joomla! osthemeclub · timetable_schedule 2018-09-28 critical9.8 CVE-2018-17385 SQL Injection exists in the Social Factory 3.8.3 component for Joomla! thephpfactory · social_factory 2018-09-28 critical9.8 CVE-2018-17384 SQL Injection exists in the Swap Factory 2.2.1 component for Joomla! thephpfactory · swap_factory 2018-09-28 critical9.8 CVE-2018-17383 SQL Injection exists in the Collection Factory 4.1.9 component for Joomla! thephpfactory · collection_factory 2018-09-28 critical9.8 CVE-2018-17382 SQL Injection exists in the Jobs Factory 2.0.4 component for Joomla! thephpfactory · jobs_factory 2018-09-28 critical9.8 CVE-2018-17380 SQL Injection exists in the Article Factory Manager 4.3.9 component for Joomla! thephpfactory · article_factory_manager 2018-09-28 critical9.8 CVE-2018-17379 SQL Injection exists in the Raffle Factory 3.5.2 component for Joomla! thephpfactory · raffle_factory 2018-09-28 critical9.8 CVE-2018-17378 SQL Injection exists in the Penny Auction Factory 2.0.4 component for Joomla! thephpfactory · penny_auction_factory 2018-09-28 critical9.8 CVE-2018-17377 SQL Injection exists in the Questions 1.4.3 component for Joomla! extensiondeveloper · questions 2018-09-28 critical9.8 CVE-2018-17376 SQL Injection exists in the Reverse Auction Factory 4.3.8 component for Joomla! thephpfactory · reverse_auction_factory 2018-09-28 critical9.8 CVE-2018-17375 SQL Injection exists in the Music Collection 3.0.3 component for Joomla! joomlathat · music_collection 2018-09-28 critical9.8 CVE-2018-14592 The CWJoomla CW Article Attachments PRO extension before 2.0.7 and CW Article Attachments FREE extension before 1.0.6 for Joomla! cwjoomla · cw_article_attachments_free, cwjoomla · cw_article_attachments_pro 2018-09-20 critical9.8 CVE-2018-17254 The JCK Editor component 6.4.4 for Joomla! arkextensions · jck_editor 2018-09-20 critical9.8 CVE-2018-15882 An issue was discovered in Joomla! joomla · joomla\! 2018-08-29 high7.5 CVE-2018-15881 An issue was discovered in Joomla! joomla · joomla\! 2018-08-29 medium5.4 CVE-2018-15880 An issue was discovered in Joomla! joomla · joomla\! 2018-08-29 critical9.8 CVE-2017-18345 The Joomanager component through 2.0.0 for Joomla! joomanager_project · joomanager 2018-08-26

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.