Skip to content
Noroxi
CVE-2019-6340· NVD / CVE Program· CNA drupal

Drupal core - Highly critical - Remote Code Execution

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

HighCVSS 8.1 · v3.1KEVWeaponized Fix available
Published
Feb 21, 2019
Updated
Jun 16, 2026
EPSS
92.0% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

90

Now

Patch today or shut off access.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
30 / 30 · Listed
EPSS
28 / 30 · 92.0%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Mar 25, 2022. That signals real attacks, not theory.

Remediation deadline for government agencies: Apr 15, 2022.

Affected systems

VendorProduct
drupaldrupal

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • drupal drupal8.5.0 and later · before 8.5.11
  • drupal drupal8.6.0 and later · before 8.6.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (drupal). Independent of NVD's CPE analysis and usually ahead of it.

  • Drupal Drupal Core

    • 8.5 and later · before 8.5.11affected
    • 8.6 and later · before 8.6.10affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistdrupal/corefrom 7.0.0 · before 7.62.07.62.0
Packagistdrupal/corefrom 8.0.0 · before 8.5.118.5.11
Packagistdrupal/corefrom 8.6.0 · before 8.6.108.6.10
Packagistdrupal/drupalfrom 7.0.0 · before 7.62.07.62.0
Packagistdrupal/drupalfrom 8.0.0 · before 8.5.118.5.11
Packagistdrupal/drupalfrom 8.6.0 · before 8.6.108.6.10

Same product

drupal: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-7602Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-004KEV
    99Now
  • CVE-2018-7600Drupal 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 oKEV
    99Now
  • CVE-2020-13671Drupal core does not properly sanitize certain filenames on uploaded files, which can lead to files being interpreted as the incorrect extenKEV
    76This week
  • CVE-2026-9082Drupal core - Highly critical - SQL injection - SA-CORE-2026-004KEV
    74This week
  • CVE-2014-3704The expandArguments function in the database abstraction API in Drupal core 7.x before 7.32 does not properly construct prepared statements,
    60This week
  • CVE-2019-6339PHAR stream wrapper Arbitrary PHP code execution
    50Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:drupal/core7.62.0Package registry (OSV)
Packagist:drupal/core8.5.11Package registry (OSV)
Packagist:drupal/core8.6.10Package registry (OSV)
Packagist:drupal/drupal7.62.0Package registry (OSV)
Packagist:drupal/drupal8.5.11Package registry (OSV)
Packagist:drupal/drupal8.6.10Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Exploit-DB entry ×4
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×11

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entryremote2019-03-07
Exploit-DB entryremote2019-03-07
Exploit-DB entrywebapps2019-02-23
Exploit-DB entrywebapps2019-02-25
Metasploit moduleexploit/unix/webapp/drupal_restws_unserializeDrupal RESTful Web Services unserialize() RCEexploit2019-02-20
Nuclei detection templateNuclei template CVE-2019-6340 —
Proof-of-concept repository on GitHubstars:302019-02-22
Proof-of-concept repository on GitHubstars:422019-02-23
Proof-of-concept repository on GitHubstars:22019-02-25
Proof-of-concept repository on GitHubstars:122019-02-25
Proof-of-concept repository on GitHubstars:02019-02-26
Proof-of-concept repository on GitHubstars:02019-03-12

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-2 d
  2. Published
  3. First PoCsame day
  4. CISA KEV+1127 d
  5. TodaySep 30, 2026+2778 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

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

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records