How severe is CVE-2018-7602?

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

Which packages are affected by CVE-2018-7602?

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

How do I fix CVE-2018-7602?

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

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2018-7602 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.

How does O3 Security protect against CVE-2018-7602?

O3 pinpoints whether CVE-2018-7602 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 10 known exploit references for CVE-2018-7602, including 2 documented proof-of-concept exploits on Exploit-DB and 6 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-7602?

CVE-2018-7602 has an EPSS (Exploit Prediction Scoring System) score of 99.2%, 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-7602 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-7602 (Drupal Core Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-04-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-04. 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-7602?

CVE-2018-7602 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

A Nuclei detection template exists for CVE-2018-7602, 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-7602 published, and has it been updated?

CVE-2018-7602 was published on July 19, 2018 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-04-13 — agencies required to remediate by 2022-05-04 · Ransomware

🐘 Packagist

CVE-2018-7602

CRITICAL

Drupal Core Remote Code Execution Vulnerability

Also known asDRUPAL-CORE-2018-004GHSA-297x-j9pm-xjgg

Published

Jul 19, 2018

Updated

Jul 8, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

10 known

EPSS Exploitation Probability

via FIRST.org ↗

99.2%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘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

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 7.0&&< 7.59	7.59
🐘Packagist	`drupal/core`	≥ 8.0&&< 8.4.8	8.4.8
🐘Packagist	`drupal/core`	≥ 8.5&&< 8.5.3	8.5.3
🐘Packagist	`drupal/drupal`	≥ 7.0&&< 7.59	7.59
🐘Packagist	`drupal/drupal`	≥ 8.0&&< 8.4.8	8.4.8
🐘Packagist	`drupal/drupal`	≥ 8.5&&< 8.5.3	8.5.3

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-44557webappsphp✓ Verified

Drupal < 7.58 - 'Drupalgeddon3' (Authenticated) Remote Code (Metasploit)

by SixP4ck3r · Apr 30, 2018

Exploit-DB Source

EDB-44542webappsphp✓ Verified

Drupal < 7.58 - 'Drupalgeddon3' (Authenticated) Remote Code Execution (PoC)

by Blaklis · Apr 25, 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update drupal/core to 7.59 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-7602 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 O3 protects you
O3 pinpoints whether CVE-2018-7602 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2018-7602. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-7602 in your dependencies?

O3 detects CVE-2018-7602 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works