NetSight

Security Dashboard

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

Reset
200 matching advisories · page 6 of 7Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2022-43967 Concrete CMS vulnerable to Cross-site Scripting via multilingual report composer · concrete5/concrete5 2022-11-14 medium6.5 CVE-2022-43686 Concrete CMS vulnerable to Uncontrolled Resource Consumption leading to DoS composer · concrete5/concrete5 2022-11-14 medium6.1 CVE-2022-43694 Concrete CMS vulnerable to Reflected Cross-site Scripting via image manipulation library composer · concrete5/concrete5 2022-11-14 medium6.1 CVE-2022-43692 Concrete CMS vulnerable to Reflected Cross-site Scripting composer · concrete5/concrete5 2022-11-14 high8.8 CVE-2022-43693 Concrete CMS vulnerable to Cross-site Request Forgery composer · concrete5/concrete5 2022-11-14 medium6.1 CVE-2022-30120 Cross site scripting in Concrete CMS composer · concrete5/core 2022-06-24 medium6.1 CVE-2022-30119 XSS in /dashboard/reports/logs/view - old browsers only. concretecms · concrete_cms 2022-06-24 medium6.1 CVE-2022-30118 Title for CVE: XSS in /dashboard/system/express/entities/forms/save_control/[GUID]: old browsers only.Description: When using Internet Explorer with the XSS pr… concretecms · concrete_cms 2022-06-24 critical9.1 CVE-2022-30117 Path traversal in Concrete CMS composer · concrete5/core 2022-06-24 critical9.8 CVE-2022-21829 Code injection in concrete CMS composer · concrete5/core 2022-06-24 high8.8 CVE-2021-22954 Cross Site Request Forgery in concrete5/concrete5 composer · concrete5/concrete5 2022-02-09 high7.2 CVE-2021-40101 An issue was discovered in Concrete CMS before 8.5.7. concretecms · concrete_cms 2021-11-30 high7.5 CVE-2021-22970 Server-Side Request Forgery in Concrete CMS composer · concrete5/core 2021-11-19 medium5.3 CVE-2021-22969 Server-Side Request Forgery in Concrete CMS composer · concrete5/core 2021-11-19 high7.2 CVE-2021-22968 Improper file handling in concrete5/core composer · concrete5/core 2021-11-19 high7.5 CVE-2021-22967 Exposure of sensitive information in concrete5/core composer · concrete5/core 2021-11-19 high8.8 CVE-2021-22966 Improper Privilege Management in Concrete CMS composer · concrete5/core 2021-11-19 high7.5 CVE-2021-22951 Password exposure in concrete5/core composer · concrete5/core 2021-11-19 critical9.8 CVE-2021-22958 Server-Side Request Forgery vulnerability in concrete5 composer · concrete5/concrete5 2021-10-07 medium6.4 CVE-2021-40109 A SSRF issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 high8.8 CVE-2021-40108 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 medium6.1 CVE-2021-40106 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 medium6.1 CVE-2021-40105 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 high7.5 CVE-2021-40104 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 high7.5 CVE-2021-40103 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 critical9.8 CVE-2021-40098 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 high8.8 CVE-2021-40097 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-27 critical9.1 CVE-2021-40102 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-24 medium5.4 CVE-2021-40100 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-24 high7.2 CVE-2021-40099 An issue was discovered in Concrete CMS through 8.5.5. concretecms · concrete_cms 2021-09-24

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.