CVE-2019-6340
Published: March 25, 2022
Official Description
In Drupal Core, some field types do not properly sanitize data from non-form sources. This can lead to arbitrary PHP code execution in some cases.
CISA KEV Advisory
Drupal Core Remote Code Execution Vulnerability
In Drupal Core, some field types do not properly sanitize data from non-form sources. This can lead to arbitrary PHP code execution in some cases.
Apply updates per vendor instructions.
Risk Analysis
This vulnerability in Drupal Core allows for arbitrary PHP code execution due to improper data sanitization from non-form sources. The very high EPSS score indicates a high likelihood of exploitation, and its presence in CISA's KEV catalog confirms active exploitation. This makes it a critical vulnerability that needs immediate attention.
This vulnerability is actively exploited in the wild and is included in CISA's Known Exploited Vulnerabilities catalog. The ability to execute arbitrary PHP code can lead to full system compromise.
It is crucial to apply the latest security updates and patches for Drupal Core to address this code execution vulnerability. Implement robust input sanitization and regularly audit custom field types for proper security controls.
Technical Analysis
CVE-2019-6340 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2019-6340 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2019-6340 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1