CVE Tools

CVE-2019-6340

Drupal core - Highly critical - Remote Code Execution

Exploited in the wild. In CISA KEV since 2022‑03‑25. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, GitHub, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Drupal CoreAffected: ≥ 8.5, < 8.5.11Upgrade to: 8.5.11Affected: ≥ 8.6, < 8.6.10Upgrade to: 8.6.10Stated by: CVE record
  • Packagist drupal/coreAffected: ≥ 8.6.0, < 8.6.10Upgrade to: 8.6.10Stated by: GitHub advisory
  • Packagist drupal/drupalAffected: ≥ 7.0.0, < 7.62.0Upgrade to: 7.62.0Stated by: GitHub advisory
  • Сообщество свободного программного обеспечения DrupalAffected: от 8.0.0 до 8.5.11Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

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.)

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2022-03-25.

US federal agencies must remediate by 2022-04-15.

Apply updates per vendor instructions.
Public exploits

8 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

92% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 119 days before any public exploit.

  1. OpenVAS check added
  2. Public exploit / PoCsource: github-pocnuclei check added
  3. Patch availableworkaround available, record updated
  4. Added to CISA KEV
  5. Publishedweakness classified, att&ck mapped

Affected products

Scale

How widely the affected products are used. This is not a count of vulnerable hosts.

Estimate Public sources, each figure dated. How much of it is already patched is not known.

Drupal

Web

Usage: unknown. No public source measures this product yet.

Version split: unknown. No public source for this product.

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Drupal Core, not every advisory. This one: actively exploited.