Samuel Mortenson

The issue affects Drupal core, allowing Cross-Site Scripting (XSS) due to improper neutralization of input during web page generation.

The issue arises when the filesystem loader loads templates for which the name is a user input. It is possible to use the `source` or `include` statement to read arbitrary files from outside the templates' directory when using a namespace like `@somewhere/../some.file`. In such a case, validation is bypassed.

The issue is related to the Quick Edit module in the Drupal content management system, which does not properly check entity access in some circumstances. This could result in users with the "access in-place editing" permission viewing some content they are not authorized to access. Sites are only affected if the QuickEdit module is installed.

The issue is related to the improper sanitization of certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extension and served as the wrong MIME type or executed as PHP for certain hosting configurations. This can allow a remote attacker to execute arbitrary PHP code on the server. The estimated number of potentially affected devices worldwide is not specified.

The issue is related to a cross-site scripting vulnerability in Drupal Core, where the Drupal AJAX API does not disable JSONP by default, allowing for an XSS attack. This can potentially impact the integrity of data.

The issue is related to insufficient authentication of executed requests in the Drupal CMS system. It can be exploited by a remote attacker to execute arbitrary code. Additionally, there is a Cross Site Request Forgery vulnerability in the Drupal Core Form API, which does not properly handle certain form input from cross-site requests, potentially leading to other vulnerabilities.

An issue was discovered where certain areas displaying Markdown were not properly sanitizing some XSS payloads.

The issue arises from improper validation of certain fields when manipulating files through the file REST resource. This affects sites with the RESTful Web Services (rest) module enabled, where the file REST resource is enabled and allows PATCH requests. An attacker must have the ability to get or register a user account on the site with permissions to upload files and to modify the file resource.

The issue allows critical access bypass by authenticated users if the RESTful Web Services (rest) module is enabled and the site allows PATCH requests.

The issue affects some administrative paths that did not include protection for CSRF, allowing an attacker to disable certain blocks on a site. This is mitigated by the requirement for an attacker to know the block ID.

The issue allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks. This is due to an incomplete fix for a previous issue.