Is CVE-2019-6340 exploited in the wild?

Yes. CVE-2019-6340 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.

How severe is CVE-2019-6340?

Critical severity, with a CVSS score of 3, published 13 May 2022.

Which products and versions are affected?

drupal/core (Packagist) ECOSYSTEM:introduced=8.0.0,fixed=8.5.11|ECOSYSTEM:introduced=8.6.0,fixed=8.6.10, ECOSYSTEM:introduced=8.6.0,fixed=8.6.10; drupal/drupal (Packagist) ECOSYSTEM:introduced=7.0.0,fixed=7.62.0.

Is there a fix for CVE-2019-6340?

Yes. drupal/core (Packagist): upgrade to 8.5.11, 8.6.10 or later; drupal/drupal (Packagist): upgrade to 7.62.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2019-6340 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2019-6340?

Check whether you run Drupal Core, drupal/core (Packagist) or drupal/drupal (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2019-6340: Drupal Core Remote Code Execution Vulnerability

CVE-2019-6340 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2022-05-13

Drupal Core contains a remote code execution vulnerability due to improper sanitization of data from non-form sources in certain field types. An attacker can exploit this by sending malicious PATCH or POST requests to sites with RESTful Web Services or similar modules enabled, potentially leading to arbitrary PHP code execution.

Technologies: Drupal Core, drupal/core (Packagist), drupal/drupal (Packagist). Vendors: Drupal, Packagist.

Quick answers

Is CVE-2019-6340 exploited in the wild?: Yes. CVE-2019-6340 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.
How severe is CVE-2019-6340?: Critical severity, with a CVSS score of 3, published 13 May 2022.
Which products and versions are affected?: drupal/core (Packagist) ECOSYSTEM:introduced=8.0.0,fixed=8.5.11|ECOSYSTEM:introduced=8.6.0,fixed=8.6.10, ECOSYSTEM:introduced=8.6.0,fixed=8.6.10; drupal/drupal (Packagist) ECOSYSTEM:introduced=7.0.0,fixed=7.62.0.
Is there a fix for CVE-2019-6340?: Yes. drupal/core (Packagist): upgrade to 8.5.11, 8.6.10 or later; drupal/drupal (Packagist): upgrade to 7.62.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2019-6340 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2019-6340?: Check whether you run Drupal Core, drupal/core (Packagist) or drupal/drupal (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

drupal/core (Packagist): upgrade to 8.5.11, 8.6.10 or later
```
composer require drupal/core:^8.6.10
```
drupal/drupal (Packagist): upgrade to 7.62.0 or later
```
composer require drupal/drupal:^7.62.0
```

Affected products

Drupal Drupal Core 8.5.x before 8.5.11, 8.6.x before 8.6.10

Identifiers

CVE-2019-6340
DRUPAL-CORE-2019-003
GHSA-3gx6-h57h-rm27

Timeline

2019-02-20: disclosed: Initial advisory date based on CVE ID and early references.
2022-03-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.
2019-03-05: exploited: Exploit code published on Exploit-DB.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.