Threats / Drupal / CVE-2018-7602
CVE-2018-7602
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Drupal Core vulnerability
Remote code execution vulnerability in Drupal Core affecting multiple subsystems, allowing attackers to execute arbitrary code on vulnerable Drupal installations.
Verdict
Today item, not a backlog item.
Critical remote code execution flaw in Drupal Core with high exploitability. Active exploitation in the wild and associated with ransomware campaigns indicates immediate threat to unpatched systems.
CISA KEV Yes · 2022-04-133Ransomware use Flagged3EPSS 0.99069 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-13), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99069 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Drupal, Core. Confirm exact fixed builds in the vendor advisory.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a vulnerable Drupal Core installation and craft a malicious request targeting multiple subsystems.
Business
Attackers gain initial foothold on web infrastructure hosting business-critical applications.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code on the compromised server with the privileges of the web application process.
Business
Complete compromise of application integrity and confidentiality; attacker gains ability to read, modify, or delete data.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence and move laterally to connected systems and databases.
Business
Breach expands beyond initial target; internal network and sensitive data repositories become accessible to threat actors.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware or exfiltrate sensitive business data for extortion.
Business
Operations disrupted; financial and reputational damage from data theft, encryption, or public disclosure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by drupalCNA
Credited with finding itDavid RothsteinfinderAlex PottfinderHeine DeelstrafinderJasper MattssonfinderDavid Rothsteinremediation developerxjmremediation developerSamuel Mortensonremediation developerAlex Pottremediation developerLee Rowlandsremediation developerHeine Deelstraremediation developerPere Orgaremediation developerPeter Wolaninremediation developerTim Plunkettremediation developerMichael Hessremediation developerNate Lamptonremediation developerJasper Mattssonremediation developerNeil Drummremediation developerCash Williamsremediation developerDaniel Wehnerremediation developer