Actively exploited in the wild
Drupal Core Remote Code Execution Vulnerability
Drupal - Core · Listed in the CISA KEV since 2022-03-25. This indicates confirmed attacks in production environments.
Required action: Apply updates per vendor instructions.
CVE-2019-6340
HighCVSS 8.1KEVSummary
Some field types do not properly sanitize data from non-form sources in Drupal 8.5.x before 8.5.11 and Drupal 8.6.x before 8.6.10. This can lead to arbitrary PHP code execution in some cases. A site is only affected by this if one of the following conditions is met: The site has the Drupal 8 core RESTful Web Services (rest) module enabled and allows PATCH or POST requests, or the site has another web services module enabled, like JSON:API in Drupal 8, or Services or RESTful Web Services in Drupal 7.
Risk Assessment
An attacker could exploit this vulnerability to execute arbitrary PHP code on the server, potentially leading to full site compromise.
Recommendation
Update Drupal to version 8.5.11, 8.6.10 or later, and if using Drupal 7, apply the relevant contributed module updates.
Other vulnerabilities in Drupal
See all- CVE-2017-6919High
Drupal 8 versions before 8.2.8 and 8.3 before 8.3.1 allow critical access bypass by authenticated users if the RESTful Web Services (rest) module is enabled and the site allows PATCH requests.
- CVE-2017-6377High
In Drupal 8.2.x versions before 8.2.7, when adding a private file via the editor, access permissions for the attached file are not correctly checked, leading to an access bypass.
- CVE-2016-9450High
The user password reset form in Drupal 8.x before 8.2.3 allows remote attackers to conduct cache poisoning attacks due to failure to specify a correct cache context.
- CVE-2016-3171High
Drupal 6.x before 6.38, when used with PHP before 5.4.45, 5.5.x before 5.5.29, or 5.6.x before 5.6.13, might allow remote attackers to execute arbitrary code via vectors related to session data truncation.
- CVE-2016-3165High
The Form API in Drupal 6.x before 6.38 ignores access restrictions on submit buttons, potentially allowing remote attackers to bypass intended access restrictions.
- CVE-2016-3164High
Drupal versions 6.x before 6.38, 7.x before 7.43, and 8.x before 8.0.4 may allow remote attackers to conduct open redirect attacks by leveraging (1) custom code or (2) a form shown on a 404 error page, related to path manipulation.
- CVE-2026-9082CriticalActively exploited
SQL Injection vulnerability in Drupal core. Improper neutralization of special elements in SQL commands allows an attacker to execute arbitrary SQL statements.
- CVE-2018-7602CriticalActively exploited
A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being compromised. This vulnerability is related to Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002. Both SA-CORE-2018-002 and this vulnerability are being exploited in the wild.
- CVE-2018-7600CriticalActively exploited
Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1 allows remote attackers to execute arbitrary code because of an issue affecting multiple subsystems with default or common module configurations.
- CVE-2026-8493Medium
The Colorbox Inline module for Drupal is vulnerable to Cross-Site Scripting (XSS) in all versions before 2.1.1. The vulnerability is due to improper neutralization of input during web page generation.
Original NVD description (English source)
Some field types do not properly sanitize data from non-form sources in Drupal 8.5.x before 8.5.11 and Drupal 8.6.x before 8.6.10. This can lead to arbitrary PHP code execution in some cases. A site is only affected by this if one of the following conditions is met: The site has the Drupal 8 core RESTful Web Services (rest) module enabled and allows PATCH or POST requests, or the site has another web services module enabled, like JSON:API in Drupal 8, or Services or RESTful Web Services in Drupal 7. (Note: The Drupal 7 Services module itself does not require an update at this time, but you should apply other contributed updates associated with this advisory if Services is in use.)