CVE-2018-7600

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 5 internet-exposed hosts are running an affected version right now
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 9.8Exploit: NoneExposed: 5

A fix is available — apply it.

Drupal 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 of an issue affecting multiple subsystems with default or common module configurations.

Live · internet exposure

5 internet-exposed hosts are running an affected version of CVE-2018-7600 right now.

across 5 countries (Australia, Brazil, Ireland, Spain, Switzerland)top: drupal
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
99(Act)
EG Risk 99/100SSVC: Act

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS
100.0%
KEV
⚠ Exploited

Published

March 29, 2018

Last Modified

October 31, 2025

Advisory Details (8)

Auto-updated Jun 1, 2026
⚠️ Active exploitation confirmed. Patch available.
generic

Uncovering Drupalgeddon 2 - Check Point Research

https://research.checkpoint.com/uncovering-drupalgeddon-2/
generic Patch Available

[SECURITY] [DLA 1325-1] drupal7 security update

https://lists.debian.org/debian-lts-announce/2018/03/msg00028.html
generic🔴 Active Exploitation

FAQ about SA-CORE-2018-002 | Drupal Groups

https://groups.drupal.org/security/faq-2018-002
generic

GreySec Forums

https://greysec.net/showthread.php?tid=2912&pid=10561
generic

GitHub - g0rx/CVE-2018-7600-Drupal-RCE: CVE-2018-7600 Drupal RCE · GitHub

https://github.com/g0rx/CVE-2018-7600-Drupal-RCE
generic🟡 PoC Available

GitHub - a2u/CVE-2018-7600: 💀Proof-of-Concept for CVE-2018-7600 Drupal SA-CORE-2018-002 · GitHub

https://github.com/a2u/CVE-2018-7600
generic
http://www.securitytracker.com/id/1040598
generic
http://www.securityfocus.com/bid/103534

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudrupal7 (7.44-1ubuntu1~16.04.0+esm1) @ xenial2026-07-21ubuntu

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 rangeFixed inDependents
drupal/core8.5.08.5.1—
drupal/drupal8.5.0, 8.5.0-alpha1, 8.5.0-beta1, 8.5.0-rc18.5.1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× in last 7d / 132× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 257 total refreshes for this CVE.

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

Publicly available exploits

(10 references)

Working exploit code is in the public domain (7 GitHub PoCs) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCrabbitmask/CVE-2018-7600-Drupal7
    First seen Apr 12, 2020

    CVE-2018-7600【Drupal7】批量扫描工具。

    Open source ↗
  • GitHub PoCzhzyker/CVE-2018-7600-Drupal-POC-EXP
    First seen Apr 7, 2020

    CVE-2018-7600 Drupal Drupalgeddon 2 远程代码执行漏洞利用脚本

    Open source ↗
  • GitHub PoCr3dxpl0it/CVE-2018-7600
    First seen Oct 23, 2018

    CVE-2018-7600 POC (Drupal RCE)

    Open source ↗
  • GitHub PoClorddemon/drupalgeddon2
    First seen Apr 19, 2018

    Exploit for CVE-2018-7600.. called drupalgeddon2,

    Open source ↗
  • Exploit-DBEDB-44482✓ verified
    First seen Apr 17, 2018

    Drupal < 8.3.9 / < 8.4.6 / < 8.5.1 - 'Drupalgeddon2' Remote Code Execution (Metasploit)

    Open source ↗
  • GitHub PoCpimps/CVE-2018-7600
    First seen Apr 17, 2018

    Exploit for Drupal 7 <= 7.57 CVE-2018-7600

    Open source ↗
  • GitHub PoCfirefart/CVE-2018-7600
    First seen Apr 16, 2018

    CVE-2018-7600 - Drupal 7.x RCE

    Open source ↗
  • GitHub PoCdr-iman/CVE-2018-7600-Drupal-0day-RCE
    First seen Apr 14, 2018

    Drupal 0day Remote PHP Code Execution (Perl)

    Open source ↗
  • Exploit-DBEDB-44449✓ verified
    First seen Apr 13, 2018

    Drupal < 7.58 / < 8.3.9 / < 8.4.6 / < 8.5.1 - 'Drupalgeddon2' Remote Code Execution

    Open source ↗
  • Exploit-DBEDB-44448✓ verified
    First seen Apr 13, 2018

    Drupal < 8.3.9 / < 8.4.6 / < 8.5.1 - 'Drupalgeddon2' Remote Code Execution (PoC)

    Open source ↗

Frequently asked(6)

What is CVE-2018-7600?
CVE-2018-7600 is a critical vulnerability published on March 29, 2018. Drupal 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 of an issue affecting multiple subsystems with default or common module configurations.
When was CVE-2018-7600 disclosed?
CVE-2018-7600 was first published in the National Vulnerability Database on March 29, 2018, with the most recent update on October 31, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-7600 actively exploited?
Yes. CISA added CVE-2018-7600 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Drupal Drupal Core. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2018-7600?
CVE-2018-7600 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2018-7600?
CVE-2018-7600 affects Drupal Drupal Core. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2018-7600?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-7600, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-7600

Explore →

Is Your Infrastructure Affected by CVE-2018-7600?

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

Start Free Scan →Browse All CVEs