CVE-2018-7600: Drupalgeddon2
- Vendors
- Debian ProjectDrupal
Drupalgeddon2 is an unauthenticated remote code execution vulnerability in Drupal core affecting multiple subsystems under default or common module configurations. Affected releases include 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. Improper input validation allows crafted requests to trigger arbitrary code execution through the Form API render array, including AJAX form processing. Executed code runs with the privileges of the web server process and can compromise the Drupal site.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution with web server process privileges, website compromise, and modification or deletion of website files and CMS data. Observed exploitation has installed cryptocurrency miners and botnet components and used compromised servers to launch DDoS attacks. Exploitation does not require authentication.
Mitigation
If you can’t patch tonight, do this now.
No specific validated workaround is available. Until upgrades can be applied, limit public access to affected Drupal installations. Investigate exposed servers for evidence of compromise and initiate incident response and recovery where necessary; access restrictions and patching alone do not eradicate an existing compromise.
Remediation
Patch, then assume compromise.
Upgrade Drupal core to a supported, patched release. Historical fixes for this vulnerability are Drupal 7.58, 8.3.9, 8.4.6, and 8.5.1 for their respective branches. CVE-2018-7602 is a separate, related vulnerability requiring its own patches; applying only the CVE-2018-7600 fix does not address it. Investigate previously exposed installations for compromise, because upgrading does not remove existing malware or unauthorized modifications. Historical Drupal guidance treated sites not updated by April 11, 2018, as potentially compromised.
Exploits
30 exploits validated by Mallory's analysis. Hidden: 10 rejected by Mallory's analysis as not a working exploit; 4 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2018-7600 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2018-7600?
- Yes. Mallory tracks 30 public exploits or proofs of concept for CVE-2018-7600, the earliest disclosed Mar 28, 2018.
- Is there a patch for CVE-2018-7600?
- Upgrade Drupal core to a supported, patched release. Historical fixes for this vulnerability are Drupal 7.58, 8.3.9, 8.4.6, and 8.5.1 for their respective branches.
- What products are affected by CVE-2018-7600?
- Drupal and Debian Project Debian Linux.
- How severe is CVE-2018-7600?
- CVE-2018-7600 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 100.0% (100th percentile) as of Oct 16, 2026.
Recent activity
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.