Loading vulnerability…
A remote code execution vulnerability exists in Drupal Core (7.x prior to 7.62, 8.6.x prior to 8.6.6, 8.5.x prior to 8.5.9) due to unsafe handling of the PHP phar stream wrapper. File operations on untrusted phar:// URIs can lead to execution of arbitrary PHP code if user input is not properly validated. This affects code paths in core, contributed, and custom modules that perform file operations on user-supplied input.
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 repository contains a proof-of-concept exploit for CVE-2019-6339, a remote code execution vulnerability in Drupal. The main file, drupalexploit.php, generates a malicious PHAR file ('phar.phar') with crafted metadata. The exploit leverages PHP object deserialization, embedding a GuzzleHttp\Psr7\FnStream object whose destructor calls the phpinfo() function. When a vulnerable Drupal instance processes this PHAR file (typically via file upload or deserialization), it can trigger arbitrary PHP function execution, demonstrating remote code execution. The repository is minimal, containing only a README and the exploit script, and is intended as a demonstration of the vulnerability rather than a weaponized attack tool.
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.