NetSight

Security Dashboard

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

Reset
82 matching advisories · page 3 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.6 CVE-2022-22690 Umbraco ApplicationURL Overwrite nuget · Umbraco.Cms.Core 2022-01-18 critical9.8 CVE-2021-37334 Umbraco Forms version 4.0.0 up to and including 8.7.5 and below are vulnerable to a security flaw that could lead to a remote code execution attack and/or arbi… umbraco · forms 2021-08-25 medium6.1 CVE-2021-34254 Umbraco CMS before 7.15.7 is vulnerable to Open Redirection due to insufficient url sanitization on booting.aspx. umbraco · umbraco_cms 2021-06-28 medium6.5 CVE-2020-5811 Authenticated path traversal in Umbraco CMS nuget · UmbracoCms 2020-12-30 medium5.4 CVE-2020-5810 A stored XSS vulnerability exists in Umbraco CMS <= 8.9.1 or current. umbraco · umbraco_cms 2020-12-30 medium5.4 CVE-2020-5809 Umbraco CMS vulnerable to stored XSS nuget · UmbracoCms.Core 2020-12-30 medium4.3 CVE-2020-29454 Incorrect permission enforcement in UmbracoCms nuget · UmbracoCms 2020-12-02 high7.5 CVE-2020-7685 Insecure defaults in UmbracoForms nuget · UmbracoForms 2020-07-28 medium6.5 CVE-2020-9472 Unrestricted Upload of File with Dangerous Type in Umbraco CMS nuget · UmbracoCms 2020-03-16 high8.8 CVE-2020-9471 Umbraco CMS Authenticated File Upload nuget · UmbracoCMS.Core 2020-03-16 medium4.3 CVE-2020-7210 Umbraco CMS vulnerable to CSRF nuget · UmbracoCMS.Core 2020-01-23 critical9.8 CVE-2019-13957 In Umbraco 7.3.8, there is SQL Injection in the backoffice/PageWApprove/PageWApproveApi/GetInpectSearch method via the nodeName parameter. umbraco · umbraco 2019-10-02 medium4.8 CVE-2018-17256 Umbraco CMS vulnerable to stored XSS nuget · umbraco 2018-11-27 critical9.8 CVE-2014-10074 Umbraco before 7.2.0 has a remote PHP code execution vulnerability because Umbraco.Web.UI/config/umbracoSettings.Release.config does not block the upload of .p… umbraco · umbraco_cms 2018-08-27 medium5.5 CVE-2017-15280 Umbraco CMS XXE Vulnerability nuget · UmbracoCms.Web 2017-10-12 medium5.4 CVE-2017-15279 Umbraco CMS vulnerable to stored XSS nuget · UmbracoCMS.Web 2017-10-12 critical9.8 CVE-2012-1301 The FeedProxy.aspx script in Umbraco 4.7.0 allows remote attackers to proxy requests on their behalf via the "url" parameter. umbraco · umbraco_cms 2017-04-13 medium6.1 CVE-2015-8815 Multiple cross-site scripting (XSS) vulnerabilities in Umbraco before 7.4.0 allow remote attackers to inject arbitrary web script or HTML via the name paramete… umbraco · umbraco 2017-03-03 high8.8 CVE-2015-8814 Umbraco CMS vulnerable to CSRF nuget · Umbraco.CMS 2017-03-03 high8.2 CVE-2015-8813 Umbraco CMS vulnerable to CSRF nuget · Umbraco.CMS 2017-03-03 high7.5 CVE-2013-4793 The update function in umbraco.webservices/templates/templateService.cs in the TemplateService component in Umbraco CMS before 6.0.4 does not require authentic… umbraco · umbraco_cms 2014-12-27 medium4.3 CVE-2013-0741 Cross-site scripting (XSS) vulnerability in imagegen.ashx in Percipient Studios ImageGen before 2.9.0 for Umbraco CMS allows remote attackers to inject arbitra… percipientstudios · imagen 2013-11-19

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.