CVE-2019-6340
Drupal Core Remote Code Execution
- Published21 Feb 2019
- Added to CISA KEV25 Mar 2022
- Remediation due15 Apr 2022
Description
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.)
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-6340
- https://www.drupal.org/sa-core-2019-003
- https://www.exploit-db.com/exploits/46452/
- https://www.exploit-db.com/exploits/46459/
- https://www.exploit-db.com/exploits/46510/
- https://www.synology.com/security/advisory/Synology_SA_19_09
- http://www.securityfocus.com/bid/107106
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2019-6340 being actively exploited?
Yes. CVE-2019-6340 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 25 Mar 2022.
How severe is CVE-2019-6340?
CVE-2019-6340 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 92.0% probability of exploitation.
Which products are affected by CVE-2019-6340?
Affected products include Drupal.
How do I fix CVE-2019-6340?
Upgrade affected software to a fixed version, for example Drupal 8.5.11 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2019-6340 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.