NetSight

Security Dashboard

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

Reset
1,774 matching advisories · page 22 of 60Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2022-27912 An issue was discovered in Joomla! joomla · joomla\! 2022-10-25 medium5.3 CVE-2022-27911 An issue was discovered in Joomla! joomla · joomla\! 2022-08-31 medium6.1 CVE-2022-27910 In Joomla component 'Joomlatools - DOCman 3.5.13 (and likely most versions below)' are affected to an reflected Cross-Site Scripting (XSS) in an image upload f… joomlatools · docman 2022-07-10 medium5.4 CVE-2022-29426 Authenticated (contributor or higher user role) Reflected Cross-Site Scripting (XSS) vulnerability in 2J Slideshow Team's Slideshow, Image Slider by 2J plugin … 2joomla · 2j_slideshow 2022-05-20 medium4.3 CVE-2022-27909 In Joomla component 'jDownloads 3.9.8.2 Stable' the remote user can change some parameters in the address bar and see the names of other users' files jdownloads · jdownloads 2022-05-06 high7.5 CVE-2022-23802 Joomla Guru extension 5.2.5 is affected by: Insecure Permissions. ijoomla · guru 2022-05-06 medium6.1 CVE-2022-23801 An issue was discovered in Joomla! joomla · joomla\! 2022-03-30 medium6.1 CVE-2022-23800 Cross-site Scripting (XSS) within joomla/filter class composer · joomla/filter 2022-03-30 critical9.8 CVE-2022-23799 Variable Tampering within joomla/input class composer · joomla/input 2022-03-30 medium6.1 CVE-2022-23798 An issue was discovered in Joomla! joomla · joomla\! 2022-03-30 critical9.8 CVE-2022-23797 An issue was discovered in Joomla! joomla · joomla\! 2022-03-30 medium6.1 CVE-2022-23796 An issue was discovered in Joomla! joomla · joomla\! 2022-03-30 critical9.8 CVE-2022-23795 An issue was discovered in Joomla! joomla · joomla\! 2022-03-30 medium5.3 CVE-2022-23794 Path Disclosure within joomla/filesystem class composer · joomla/filesystem 2022-03-30 high7.5 CVE-2022-23793 Path Traversal within joomla/archive tar class composer · joomla/archive 2022-03-30 critical9.1 CVE-2021-26040 An issue was discovered in Joomla! joomla · joomla\! 2021-08-24 medium6.1 CVE-2021-26039 An issue was discovered in Joomla! joomla · joomla\! 2021-07-07 high7.5 CVE-2021-26038 An issue was discovered in Joomla! joomla · joomla\! 2021-07-07 medium5.3 CVE-2021-26037 An issue was discovered in Joomla! joomla · joomla\! 2021-07-07 high7.5 CVE-2021-26036 An issue was discovered in Joomla! joomla · joomla\! 2021-07-07 medium6.1 CVE-2021-26035 An issue was discovered in Joomla! joomla · joomla\! 2021-07-07 critical9.8 CVE-2010-1435 Joomla! joomla · joomla\! 2021-06-21 high7.5 CVE-2010-1434 Joomla! joomla · joomla\! 2021-06-21 critical9.8 CVE-2010-1433 Joomla! joomla · joomla\! 2021-06-21 high7.5 CVE-2010-1432 Joomla! joomla · joomla\! 2021-06-21 medium6.5 CVE-2021-26034 An issue was discovered in Joomla! joomla · joomla\! 2021-05-26 medium6.5 CVE-2021-26033 An issue was discovered in Joomla! joomla · joomla\! 2021-05-26 medium6.1 CVE-2021-26032 An issue was discovered in Joomla! joomla · joomla\! 2021-05-26 medium5.3 CVE-2021-26031 An issue was discovered in Joomla! joomla · joomla\! 2021-04-14 medium6.1 CVE-2021-26030 An issue was discovered in Joomla! joomla · joomla\! 2021-04-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.