NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 24 of 60Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2020-15700 An issue was discovered in Joomla! joomla · joomla\! 2020-07-15 medium5.3 CVE-2020-15699 An issue was discovered in Joomla! joomla · joomla\! 2020-07-15 medium5.3 CVE-2020-15698 An issue was discovered in Joomla! joomla · joomla\! 2020-07-15 medium4.3 CVE-2020-15697 An issue was discovered in Joomla! joomla · joomla\! 2020-07-15 medium6.1 CVE-2020-15696 An issue was discovered in Joomla! joomla · joomla\! 2020-07-15 medium6.3 CVE-2020-15695 An issue was discovered in Joomla! joomla · joomla\! 2020-07-15 high8.8 CVE-2020-13996 The J2Store plugin before 3.3.13 for Joomla! j2store · j2store 2020-06-09 high7.5 CVE-2020-13763 In Joomla! joomla · joomla\! 2020-06-02 medium6.1 CVE-2020-13762 In Joomla! joomla · joomla\! 2020-06-02 medium6.1 CVE-2020-13761 In Joomla! joomla · joomla\! 2020-06-02 high8.8 CVE-2020-13760 In Joomla! joomla · joomla\! 2020-06-02 medium6.5 CVE-2020-13424 The XCloner component before 3.5.4 for Joomla! xcloner · xcloner 2020-05-23 medium5.3 CVE-2020-11891 An issue was discovered in Joomla! joomla · joomla\! 2020-04-21 medium5.3 CVE-2020-11890 An issue was discovered in Joomla! joomla · joomla\! 2020-04-21 medium5.3 CVE-2020-11889 An issue was discovered in Joomla! joomla · joomla\! 2020-04-21 critical9.8 CVE-2020-10243 An issue was discovered in Joomla! joomla · joomla\! 2020-03-16 medium6.1 CVE-2020-10242 An issue was discovered in Joomla! joomla · joomla\! 2020-03-16 high8.8 CVE-2020-10241 An issue was discovered in Joomla! joomla · joomla\! 2020-03-16 medium5.3 CVE-2020-10240 An issue was discovered in Joomla! joomla · joomla\! 2020-03-16 high8.8 CVE-2020-10239 An issue was discovered in Joomla! joomla · joomla\! 2020-03-16 high7.5 CVE-2020-10238 An issue was discovered in Joomla! joomla · joomla\! 2020-03-16 high7.2 CVE-2015-7342 JNews Joomla Component before 8.5.0 allows SQL injection via upload thumbnail, Queue Search Field, Subscribers Search Field, or Newsletters Search Field. joobi · jnews 2020-03-09 high8.8 CVE-2015-7341 JNews Joomla Component before 8.5.0 allows arbitrary File Upload via Subscribers or Templates, as demonstrated by the .php5 extension. joobi · jnews 2020-03-09 high7.2 CVE-2015-7340 JEvents Joomla Component before 3.4.0 RC6 has SQL Injection via evid in a Manage Events action. gwesystems · jevents 2020-03-09 high8.8 CVE-2015-7339 JCE Joomla Component 2.5.0 to 2.5.2 allows arbitrary file upload via a .php file extension for an image file to the /com_jce/editor/libraries/classes/browser.p… widgetfactorylimited · jce 2020-03-09 high7.2 CVE-2015-7338 SQL Injection exists in AcyMailing Joomla Component before 4.9.5 via exportgeolocorder in a geolocation_longitude request to index.php. acyba · acymailing 2020-03-09 medium4.8 CVE-2015-7344 HikaShop Joomla Component before 2.6.0 has XSS via an injected payload[/caption]. hikashop · hikashop 2020-03-09 medium4.8 CVE-2015-7343 JNews Joomla Component before 8.5.0 has XSS via the mailingsearch parameter. joobi · jnews 2020-03-09 medium5.3 CVE-2020-9364 An issue was discovered in helpers/mailer.php in the Creative Contact Form extension 4.6.2 before 2019-12-03 for Joomla!. creative-solutions · creative_contact_form 2020-03-04 critical9.8 CVE-2011-4908 TinyBrowser plugin for Joomla! tiny · tinybrowser 2020-02-12

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.