How severe is CVE-2019-6340?

CVE-2019-6340 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-6340?

CVE-2019-6340 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-6340?

Update drupal/core to version 8.6.10 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2019-6340 actively exploited in the wild?

Yes. There are 24 known exploit references for CVE-2019-6340, including 3 documented proof-of-concept exploits on Exploit-DB and 16 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-6340?

CVE-2019-6340 has an EPSS (Exploit Prediction Scoring System) score of 94.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-6340 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-6340 (Drupal Core Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-15. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-6340?

CVE-2019-6340 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-6340?

A Nuclei detection template exists for CVE-2019-6340, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-6340 published, and has it been updated?

CVE-2019-6340 was published on February 21, 2019 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-03-25 — agencies required to remediate by 2022-04-15

🐘 Packagist

CVE-2019-6340

HIGH

Drupal Core Remote Code Execution Vulnerability

Also known asDRUPAL-CORE-2019-003GHSA-3gx6-h57h-rm27

Published

Feb 21, 2019

Updated

Apr 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

24 known

EPSS Exploitation Probability

via FIRST.org ↗

94.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/drupal🐘drupal/drupal🐘drupal/drupal

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.6.0&&< 8.6.10	8.6.10
🐘Packagist	`drupal/core`	≥ 7.0.0&&< 7.62.0	7.62.0
🐘Packagist	`drupal/core`	≥ 8.0.0&&< 8.5.11	8.5.11
🐘Packagist	`drupal/drupal`	≥ 7.0.0&&< 7.62.0	7.62.0
🐘Packagist	`drupal/drupal`	≥ 8.0.0&&< 8.5.11	8.5.11
🐘Packagist	`drupal/drupal`	≥ 8.6.0&&< 8.6.10	8.6.10

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46510remotephp✓ Verified

Drupal < 8.5.11 / < 8.6.10 - RESTful Web Services unserialize() Remote Command Execution (Metasploit)

by Metasploit · Mar 7, 2019

Exploit-DB Source

EDB-46452webappsphp

Drupal < 8.6.10 / < 8.5.11 - REST Module Remote Code Execution

by Charles Fol · Feb 23, 2019

Exploit-DB Source

EDB-46459webappsphp

Drupal < 8.6.9 - REST Module Remote Code Execution

by leonjza · Feb 25, 2019

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-6340 in your stack?

O3 detects CVE-2019-6340 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works