Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2020-13664: Drupal Core arbitrary PHP code execution (CVE-2020-13664)

Published May 5, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS3.0%88th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Drupal
IdentifiersCVE-2020-13664CWE-94

CVE-2020-13664 is an arbitrary PHP code execution vulnerability in Drupal Core under certain circumstances. An attacker can trick an authenticated administrator into visiting a malicious site, which can result in creation of a carefully named directory on the server’s filesystem. With that directory in place, the attacker can then attempt to brute-force a path to achieve code execution, potentially escalating to remote code execution. Windows-based Drupal deployments are described as most likely to be affected. Affected versions include Drupal Core 8.8.x prior to 8.8.8, 8.9.x prior to 8.9.1, and 9.0.x prior to 9.0.1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in arbitrary PHP code execution in the context of the Drupal application, with potential for full remote code execution on the underlying server. This can enable complete compromise of the Drupal site and, depending on hosting configuration and privileges, broader system compromise. Windows servers are noted as most likely to be affected.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exploitability by limiting administrative exposure: prevent administrators from browsing untrusted sites while authenticated, restrict access to administrative interfaces (e.g., IP allowlisting/VPN), and harden filesystem permissions to reduce the chance of unexpected directory creation where feasible. Applying the fixed Drupal releases is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade Drupal Core to a fixed release: 8.8.8 or later (for 8.8.x), 8.9.1 or later (for 8.9.x), or 9.0.1 or later (for 9.0.x).

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DrupalDrupalapplication
FAQ

Frequently asked questions

Is CVE-2020-13664 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2020-13664 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2020-13664?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2020-13664, the earliest disclosed Sep 28, 2026.
Is there a patch for CVE-2020-13664?
Upgrade Drupal Core to a fixed release: 8.8.8 or later (for 8.8.x), 8.9.1 or later (for 8.9.x), or 9.0.1 or later (for 9.0.x).
What products are affected by CVE-2020-13664?
Drupal.
How severe is CVE-2020-13664?
CVE-2020-13664 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 3.0% (88th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.