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 4 May 2022. Known ransomware use
DrupalCMS

CVE-2018-7602

CRITICAL · 9.8 CVSS v3.1 Published 2018-07-19
Fix available
A fix is available. Upgrade to 7.59 / 8.4.8 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
A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being compromised. This vulnerability is related to Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002. Both SA-CORE-2018-002 and this vulnerability are being exploited in the wild.

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

A critical remote code execution vulnerability in Drupal 7.x and 8.x core that allows attackers to exploit multiple attack vectors, potentially resulting in full site compromise. This vulnerability is related to SA-CORE-2018-002 (Drupalgeddon 2) and was actively exploited in the wild at the time of disclosure.

MitigationImmediately update Drupal core to the latest patched version (7.58 or 8.5.1 or later) following established change management procedures, including pre-update backups and post-update functionality testing.

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.0, < 7.59>= 8.4.0, < 8.4.8>= 8.5.0, < 8.5.3
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. Identify if Drupal is installed
    Look for Drupal installation directories (sites/, modules/, themes/, index.php) or check for Drupal-specific files like CHANGELOG.txt, composer.json in web root. On Debian, run: dpkg -l | grep drupal
    Affected if Drupal core files or packages are found on the system
  2. Determine installed Drupal core version
    Check the CHANGELOG.txt file in the Drupal web root for the version number. Alternatively, run 'drush status' if available, or inspect composer.json for the 'drupal/core' version entry.
    Affected if Version cannot be determined or Drupal is not present
  3. Compare version against affected ranges
    Compare your installed version to: 7.x < 7.59, 8.4.x < 8.4.8, or 8.5.x < 8.5.3. For Debian packages, check: dpkg -l drupal7 (Debian 7/8) or drupal-core (Debian 9) and compare to the affected version list.
    Affected if Installed version falls within 7.0 to 7.58, 8.4.0 to 8.4.7, or 8.5.0 to 8.5.2
  4. Verify web accessibility of Drupal instance
    Confirm the Drupal site is reachable over HTTP/HTTPS. The vulnerability is remotely exploitable through web requests to form rendering endpoints.
    Affected if Drupal is publicly accessible and version is within the affected range

A defender is affected if their Drupal installation version is 7.0-7.58, 8.4.0-8.4.7, or 8.5.0-8.5.2 and the site is accessible over the network.

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 7.59 / 8.4.8 / 8.5.3 or later
Fixed in 7.598.4.88.5.3
Vendor patch www.drupal.org →
Interim mitigation

Immediately update Drupal core to the latest patched version (7.58 or 8.5.1 or later) following established change management procedures, including pre-update backups and post-update functionality testing.

Recommended fix High confidence

Drupal 7.59+ or latest 7.x; Drupal 8.4.8+ (8.4.x); Drupal 8.5.3+ (8.5.x); or latest stable 8.x

  1. 1. Backup your Drupal database and files completely before proceeding with any upgrade.
  2. 2. For Drupal 7.x sites: Upgrade to Drupal 7.59 or later (recommended: latest 7.x stable).
  3. 3. For Drupal 8.4.x sites: Upgrade to Drupal 8.4.8 or later.
  4. 4. For Drupal 8.5.x sites: Upgrade to Drupal 8.5.3 or later.
  5. 5. For Drupal 8.6+ sites: Ensure you are running the latest stable 8.x release which includes the fix.
  6. 6. Clear all Drupal caches after upgrade (drush cr or via admin UI).
  7. 7. Verify the upgrade by checking the Drupal version at admin/reports/status.
  8. 8. For Debian systems running Drupal from packages: Apply Debian security updates (apt-get update && apt-get upgrade drupal*).
Caveat Major version upgrades (e.g., 7.x to 8.x) may require code and theme updates; minor version upgrades within same branch typically have minimal breaking changes

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

Fix this in Drupal Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7602 — 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-7602 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