Threats / Drupal / CVE-2019-6340
CVE-2019-6340
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Drupal Core vulnerability
Drupal Core field types fail to sanitize data from non-form sources, enabling arbitrary PHP code execution through deserialization of untrusted input.
Verdict
Today item — known-exploited.
An unauthenticated attacker can execute arbitrary PHP code on affected Drupal installations by exploiting improper data sanitization in field type handlers, leading to complete system compromise.
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
12 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-03-25).
Probability (EPSS)
EPSS 0.91919 — 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.
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 craft a malicious serialized PHP object and send it to a vulnerable Drupal endpoint that processes field data outside normal form submission.
Business
The organization's web application is compromised, allowing attackers to access sensitive data, modify content, and pivot to internal systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary PHP code with the privileges of the web server process to establish persistence and lateral movement.
Business
Attackers maintain long-term access to infrastructure, exfiltrate customer data, and potentially compromise connected systems and databases.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the compromised server to launch attacks against other systems on the network or use it as a staging point for further exploitation.
Business
The breach expands beyond the initial vulnerability, affecting multiple systems, increasing incident response costs, and extending the attack surface.
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