How severe is CVE-2018-7600?

CVE-2018-7600 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-7600?

CVE-2018-7600 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-7600?

Update drupal/core to 7.58 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7600 is resolved across your whole dependency graph.

How do I detect CVE-2018-7600 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-7600 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-7600 actively exploited in the wild?

Yes. There are 48 known exploit references for CVE-2018-7600, including 3 documented proof-of-concept exploits on Exploit-DB and 26 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-7600?

CVE-2018-7600 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2018-7600 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-7600 (Drupal Core Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2018-7600?

CVE-2018-7600 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2018-7600?

A Nuclei detection template exists for CVE-2018-7600, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-7600 published, and has it been updated?

CVE-2018-7600 was published on March 29, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2018-7600 — core

CRITICAL

CVE-2018-7600 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in drupal/core. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) and has been used in ransomware campaigns — treat it as actively exploited and patch now. A fix is available for drupal/core — see the affected versions and patch details below.

Drupal Core Remote Code Execution Vulnerability

Also known asDRUPAL-CORE-2018-002GHSA-7fh9-933g-885p

Published

Mar 29, 2018

Updated

Oct 24, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

48 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-05-03.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2018-7600.

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2018-7600 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

8 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/drupal🐘drupal/drupal🐘drupal/drupal🐘drupal/drupal

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 7.0&&< 7.58	7.58`composer require drupal/core:^7.58`
🐘Packagist	`drupal/core`	≥ 8.0&&< 8.3.9	8.3.9`composer require drupal/core:^8.3.9`
🐘Packagist	`drupal/core`	≥ 8.4.0&&< 8.4.6	8.4.6`composer require drupal/core:^8.4.6`
🐘Packagist	`drupal/core`	≥ 8.5.0&&< 8.5.1	8.5.1`composer require drupal/core:^8.5.1`
🐘Packagist	`drupal/drupal`	≥ 7.0&&< 7.58	7.58`composer require drupal/drupal:^7.58`
🐘Packagist	`drupal/drupal`	≥ 8.0&&< 8.3.9	8.3.9`composer require drupal/drupal:^8.3.9`

Affected Products

2 products · 7 configurations

debian linuxdebian

3 versions

7.08.09.0

Application

drupaldrupal

≥ 8.5.0 && ≤ 7.57

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-44449webappsphp✓ Verified

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

by Hans Topo & g0tmi1k · Apr 13, 2018

Exploit-DB Source

EDB-44482remotephp✓ Verified

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

by José Ignacio Rojo · Apr 17, 2018

Exploit-DB Source

EDB-44448webappsphp✓ Verified

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

by Vitalii Rudnykh · Apr 13, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 7.58 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7600 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2018-7600

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2018-7600 -u https://target

Template: Drupal - Remote Code Execution
Severity: critical
Impact: Successful exploitation allows an unauthenticated attacker to execute arbitrary code on the server, leading to full compromise of the Drupal host and its data.
Remediation: Upgrade to the latest version of Drupal or apply the official patch provided by the Drupal security team.

Template by ProjectDiscovery nuclei-templates (pikpikcu, diedromeo), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-7600 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2018-7600 — core

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2018-7600

Frequently Asked Questions

Is CVE-2018-7600 in your dependencies?