dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022. Known ransomware use
DrupalCMS

CVE-2018-7600

CRITICAL · 9.8 CVSS v3.1 Published 2018-03-29
Fix available
A fix is available. Upgrade to 8.3.9 / 8.4.6 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CVE-2018-7600 (Drupalgeddon2) is a critical remote code execution vulnerability in Drupal CMS affecting versions 7.x before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1. The flaw exists in multiple subsystems with default or common module configurations, allowing unauthenticated remote attackers to execute arbitrary code on the underlying server.

MitigationImmediately update affected Drupal installations to version 7.58, 8.3.9, 8.4.6, 8.5.1 or later. If immediate patching is not possible, implement Web Application Firewall rules to mitigate exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DrupalCMS
Affected:<= 7.57>= 8.0.0, < 8.3.9>= 8.4.0, < 8.4.6>= 8.5.0, < 8.5.1
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Drupal core version
    Inspect the CHANGELOG.txt file in the Drupal root directory, or run `grep 'VERSION' includes/bootstrap.inc` on the command line, or check the Drupal admin dashboard at /admin/reports/status
    Affected if The installed version is 7.x before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, or 8.5.x before 8.5.1
  2. Check Debian Linux version if applicable
    Run `cat /etc/debian_version` or `lsb_release -a` on the server command line
    Affected if The Debian version is 7.0, 8.0, or 9.0 and runs Drupal
  3. Verify unauthenticated access to Drupal forms
    Confirm that the Drupal site allows anonymous access to user-related forms such as /user/password (password reset), /user/register (registration), or comment submission forms without authentication
    Affected if Unauthenticated access to these forms is enabled, which is the default Drupal configuration and required for the exploit to work
  4. Identify exposed form API endpoints
    Review web server access logs for requests to /user/password, /user/register, or other form URLs using common paths like `grep -E '(/user/|form|q=)' access.log | head -20`
    Affected if These endpoints are publicly accessible and the Drupal version falls within the affected ranges

A system is affected if it runs Drupal core version 7.x before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, or 8.5.x before 8.5.1 (or Debian 7.0/8.0/9.0 with Drupal) with unauthenticated access to user-related form endpoints enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.3.9 / 8.4.6 / 8.5.1 or later
Fixed in 8.3.98.4.68.5.1
Vendor patch github.com →
Interim mitigation

Immediately update affected Drupal installations to version 7.58, 8.3.9, 8.4.6, 8.5.1 or later. If immediate patching is not possible, implement Web Application Firewall rules to mitigate exploitation attempts.

Recommended fix High confidence

Drupal 7.58, 8.3.9, 8.4.6, or 8.5.1 (or later stable versions)

  1. 1. Backup your Drupal database and files before performing any upgrade
  2. 2. Identify your current Drupal version by checking the CHANGELOG.txt file or the Drupal core status report at admin/reports/status
  3. 3. For Drupal 7.x: Upgrade to Drupal 7.58 or later
  4. 4. For Drupal 8.3.x: Upgrade to Drupal 8.3.9 or later
  5. 5. For Drupal 8.4.x: Upgrade to Drupal 8.4.6 or later
  6. 6. For Drupal 8.5.x: Upgrade to Drupal 8.5.1 or later
  7. 7. Run database updates after upgrading (update.php or drush updatedb)
  8. 8. Clear all Drupal caches after the upgrade
Caveat Minor point releases typically have few breaking changes, but test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drupal Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7600 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7600 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data