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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This six-file repository is an operational Python proof of concept for CVE-2020-13664, targeting Drupal Core's simpletest User-Agent validation. poc.py is the main entry point and implements CSRF generation, response/header-based creation-time guessing, HMAC User-Agent brute forcing and regeneration, malicious Drupal installation against an attacker database, and a watchdog-table deserialization chain. The chain uses a serialized GuzzleHttp Cookie FileCookieJar object to write a PHP shell, then triggers it through Drupal's database-log report route. serializer.php is a local helper for producing/verifying the PHP serialized gadget. requirements.txt supplies BeautifulSoup and MySQL Connector/Python. docker-compose.yml provides a local Drupal 8.8.7 and MySQL 5.7 test environment, while README.md documents the CSRF, brute-force, takeover, and shell stages. The default configuration contains an attacker database IP, MySQL port 3306, and hard-coded database/site/admin credentials; these are intended to be edited by the operator.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.