CVE-2019-6340

CRITICALNVD 8.19.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.1 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.1 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2022-2184 (ENISA EUVD) · GHSA-3gx6-h57h-rm27 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 92%CVSS: 8.1Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

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 v3
8.1
EG Score
9.0CRITICALhigh confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
92%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.1 HIGH.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
92% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-6340

Published

February 21, 2019

Last Modified

November 7, 2025

Advisory Details (6)

Auto-updated Oct 26, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

Drupal core - Highly critical - Remote Code Execution - SA-CORE-2019-003 | Drupal.org

https://www.drupal.org/sa-core-2019-003
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/107106
Web page

Synology_SA_19_09 | Synology Inc.

https://www.synology.com/security/advisory/Synology_SA_19_09
Web page

Drupal < 8.6.9 - REST Module Remote Code Execution - PHP webapps Exploit

https://www.exploit-db.com/exploits/46459/
Web page

Drupal < 8.6.10 / < 8.5.11 - REST Module Remote Code Execution - PHP webapps Exploit

https://www.exploit-db.com/exploits/46452/
Web page

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

https://www.exploit-db.com/exploits/46510/

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerdrupal/core @ 8.6.10 (fixes >= 8.6.0, < 8.6.10)—ghsa
composerdrupal/core @ 7.62.0 (fixes >= 7.0.0, < 7.62.0)—ghsa
composerdrupal/core @ 8.5.11 (fixes >= 8.0.0, < 8.5.11)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFix by version rangeDependents
drupal/core8.0.0 ... 8.5.9 (76 versions)
  • 8.0.0 up to 8.5.11: fixed in 8.5.11
  • 8.6.0 up to 8.6.10: fixed in 8.6.10
  • 7.0.0 up to 7.62.0: fixed in 7.62.0
—
drupal/drupal8.6.0 ... 8.6.9 (10 versions)
  • 7.0.0 up to 7.62.0: fixed in 7.62.0
  • 8.0.0 up to 8.5.11: fixed in 8.5.11
  • 8.6.0 up to 8.6.10: fixed in 8.6.10
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 164 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 64 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 21:32 UTCEG score recompute
  2. 2026-11-01 21:32 UTCGHSA enrichmentGHSA-3gx6-h57h-rm27 · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-11-01 08:39 UTCGHSA enrichmentGHSA-3gx6-h57h-rm27 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-01 08:39 UTCEG score recompute
  5. 2026-10-31 22:59 UTCEG score recompute
  6. 2026-10-31 00:27 UTCEG score recompute
  7. 2026-10-30 01:56 UTCEG score recompute
  8. 2026-10-29 03:24 UTCEG score recompute
  9. 2026-10-28 04:53 UTCEG score recompute
  10. 2026-10-27 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  11. 2026-10-27 06:21 UTCEG score recompute
  12. 2026-10-26 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  13. 2026-10-25 18:57 UTCEG score recompute
  14. 2026-10-25 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  15. 2026-10-25 09:18 UTCEG score recompute
  16. 2026-10-24 10:46 UTCEG score recompute
  17. 2026-10-23 12:13 UTCEG score recompute
  18. 2026-10-22 13:39 UTCEG score recompute
  19. 2026-10-21 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  20. 2026-10-20 16:33 UTCEG score recompute
  21. 2026-10-19 17:59 UTCEG score recompute
  22. 2026-10-19 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  23. 2026-10-18 19:26 UTCEG score recompute
  24. 2026-10-18 16:27 UTCEPSS rescoreEPSS 92% · 99th percentile
  25. 2026-10-18 09:43 UTCEG score recompute
Show 75 more
  1. 2026-10-17 20:53 UTCEG score recompute
  2. 2026-10-16 22:21 UTCEG score recompute
  3. 2026-10-15 23:49 UTCEG score recompute
  4. 2026-10-15 01:16 UTCEG score recompute
  5. 2026-10-14 16:28 UTCEPSS rescoreEPSS 92% · 99th percentile
  6. 2026-10-14 02:45 UTCEG score recompute
  7. 2026-10-13 16:28 UTCEPSS rescoreEPSS 92% · 99th percentile
  8. 2026-10-12 19:53 UTCEG score recompute
  9. 2026-10-11 21:13 UTCEG score recompute
  10. 2026-10-11 17:02 UTCEG score recompute
  11. 2026-10-11 12:53 UTCEG score recompute
  12. 2026-10-08 01:41 UTCEG score recompute
  13. 2026-10-07 23:43 UTCEPSS rescoreEPSS 92% · 99th percentile
  14. 2026-09-29 01:19 UTCEG score recompute
  15. 2026-09-27 21:51 UTCCISA KEV update
  16. 2026-09-26 02:36 UTCEG score recompute
  17. 2026-09-26 00:20 UTCEPSS rescoreEPSS 92% · 99th percentile
  18. 2026-09-25 19:35 UTCCISA KEV update
  19. 2026-09-25 14:55 UTCCISA KEV update
  20. 2026-09-24 19:31 UTCCISA KEV update
  21. 2026-09-24 17:13 UTCEG score recompute
  22. 2026-09-24 13:59 UTCEPSS rescoreEPSS 92% · 99th percentile
  23. 2026-09-22 19:36 UTCCISA KEV update
  24. 2026-09-22 15:25 UTCEG score recompute
  25. 2026-09-22 14:43 UTCEPSS rescoreEPSS 92% · 99th percentile
  26. 2026-09-21 22:49 UTCEG score recompute
  27. 2026-09-21 20:28 UTCEPSS rescoreEPSS 92% · 99th percentile
  28. 2026-09-21 19:09 UTCCISA KEV update
  29. 2026-09-18 20:07 UTCEG score recompute
  30. 2026-09-18 19:23 UTCEPSS rescoreEPSS 92% · 99th percentile
  31. 2026-09-18 19:20 UTCCISA KEV update
  32. 2026-09-18 14:15 UTCCISA KEV update
  33. 2026-09-16 14:10 UTCCISA KEV update
  34. 2026-09-15 04:45 UTCEG score recompute
  35. 2026-09-15 03:06 UTCEPSS rescoreEPSS 92% · 99th percentile
  36. 2026-09-14 19:24 UTCCISA KEV update
  37. 2026-09-11 18:49 UTCCISA KEV update
  38. 2026-09-10 19:28 UTCCISA KEV update
  39. 2026-09-10 12:38 UTCEG score recompute
  40. 2026-09-09 19:08 UTCCISA KEV update
  41. 2026-09-08 18:54 UTCCISA KEV update
  42. 2026-09-06 16:58 UTCEG score recompute
  43. 2026-09-06 13:44 UTCEPSS rescoreEPSS 92% · 99th percentile
  44. 2026-09-05 16:02 UTCEG score recompute
  45. 2026-09-05 15:24 UTCEPSS rescoreEPSS 92% · 99th percentile
  46. 2026-09-04 17:38 UTCCISA KEV update
  47. 2026-09-04 06:40 UTCEG score recompute
  48. 2026-09-02 17:33 UTCCISA KEV update
  49. 2026-08-31 14:19 UTCCISA KEV update
  50. 2026-08-30 22:19 UTCEG score recompute
  51. 2026-08-29 00:34 UTCEG score recompute
  52. 2026-08-27 17:22 UTCCISA KEV update
  53. 2026-08-26 17:41 UTCCISA KEV update
  54. 2026-08-24 18:52 UTCCISA KEV update
  55. 2026-08-24 16:38 UTCEG score recompute
  56. 2026-08-24 12:28 UTCEG score recompute
  57. 2026-08-21 16:49 UTCCISA KEV update
  58. 2026-08-20 17:06 UTCCISA KEV update
  59. 2026-08-19 20:25 UTCEG score recompute
  60. 2026-08-19 17:33 UTCCISA KEV update
  61. 2026-08-19 17:00 UTCEPSS rescoreEPSS 92% · 99th percentile
  62. 2026-08-18 16:58 UTCCISA KEV update
  63. 2026-08-18 15:20 UTCEG score recompute
  64. 2026-08-18 13:44 UTCEPSS rescoreEPSS 92% · 99th percentile
  65. 2026-08-17 13:56 UTCCISA KEV update
  66. 2026-08-16 05:01 UTCEG score recompute
  67. 2026-08-11 19:32 UTCCISA KEV update
  68. 2026-08-11 17:10 UTCEG score recompute
  69. 2026-08-08 18:40 UTCEG score recompute
  70. 2026-08-08 16:33 UTCEPSS rescoreEPSS 92% · 99th percentile
  71. 2026-08-07 17:09 UTCCISA KEV update
  72. 2026-08-06 16:53 UTCEG score recompute
  73. 2026-08-05 17:25 UTCCISA KEV update
  74. 2026-08-04 17:02 UTCCISA KEV update
  75. 2026-08-03 19:22 UTCCISA KEV update

Publicly available exploits

(11 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 3 Exploit-DB entries, 6 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-46510✓ verified
    Published Mar 7, 2019

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

    Open source ↗
  • Metasploitexploit/unix/webapp/drupal_restws_unserialize✓ verified
    Published Mar 6, 2019

    Drupal RESTful Web Services unserialize() RCE

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-6340.yaml
    Published Nov 21, 2020

    Drupal - Remote Code Execution

    Open source ↗
  • GitHub PoCludy-dev/drupal8-REST-RCE
    Published Aug 31, 2020

    (CVE-2019-6340, CVE-2018-7600) drupal8-REST-RCE

    Open source ↗
  • GitHub PoCjas502n/CVE-2019-6340
    Published May 27, 2019

    Drupal8's REST RCE, SA-CORE-2019-003, CVE-2019-6340

    Open source ↗
  • Exploit-DBEDB-46459
    Published Feb 25, 2019

    Drupal < 8.6.9 - REST Module Remote Code Execution

    Open source ↗
  • GitHub PoCDevDungeon/CVE-2019-6340-Drupal-8.6.9-REST-Auth-Bypass
    Published Feb 25, 2019

    CVE-2019-6340 Drupal 8.6.9 REST Auth Bypass examples

    Open source ↗
  • GitHub PoCoways/CVE-2019-6340
    Published Feb 25, 2019

    CVE-2019-6340 POC Drupal rce

    Open source ↗
  • Exploit-DBEDB-46452
    Published Feb 23, 2019

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

    Open source ↗
  • GitHub PoCknqyf263/CVE-2019-6340
    Published Feb 23, 2019

    Environment for CVE-2019-6340 (Drupal)

    Open source ↗

Frequently asked(6)

What is CVE-2019-6340?
CVE-2019-6340 is a critical-severity vulnerability; its CVE record was published on February 21, 2019. 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…
When was CVE-2019-6340 made public?
CVE-2019-6340 was made public on February 21, 2019: that is the date its CVE record's CNA, Drupal.org, gives for when the vulnerability was made public. The CVE record itself was published on February 21, 2019. EchelonGraph's copy of the record carries a last-modified date of November 7, 2025; the record at its source may have been updated since.
Is CVE-2019-6340 actively exploited?
Yes. CISA added CVE-2019-6340 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Drupal Core. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-6340?
CVE-2019-6340 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2019-6340?
CVE-2019-6340 affects Drupal Core. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-6340?
A fix for CVE-2019-6340 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-6340

Explore →

Is Your Infrastructure Affected by CVE-2019-6340?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.