basicsecurity.net
Proof, not just disclosure.
Threats / Drupal / CVE-2018-7602
CVE-2018-7602 · EUVD no mirror located · GCVE no mirror located Verified 2026-08-04

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-134Ransomware use Flagged4EPSS 0.99236 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99236 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Drupal, Core. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA-ADP ↗Reported
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
CISA-ADP ↗Reported
Currency of the record
CISA added this to its KEV catalog 1364 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
nuclei ↗Confirmed
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 8 reported-exploitation source(s)
  • CVSS 9.8 — CISA-assigned (CVE.org ADP)
  • CISA SSVC triage disposition (CVE.org ADP)
  • Public exploit availability
  • Catalogued by drupal (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2