Loading vulnerability…
CVE-2021-32708 affects league/flysystem 1.x and 2.x, a PHP file storage library. The vulnerable behavior is Flysystem's normalization of user-supplied paths or filenames by removing Unicode whitespace characters. Under specific application conditions, this can create a mismatch between validation and final stored filename handling: an application may inspect the original supplied pathname against an extension deny-list, while Flysystem later removes Unicode whitespace from the extension during normalization. An attacker can abuse this by supplying an uploaded filename or path containing Unicode whitespace in the extension so that it bypasses deny-list checks before normalization, but is ultimately stored with an executable PHP extension after normalization. If the uploaded file is placed in a web-accessible directory where PHP execution is permitted, this can result in arbitrary code execution. The vendor fixed the issue by replacing Unicode whitespace removal with rejection via exception.
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 provides an exploit and a scanner for CVE-2021-32708, a vulnerability in league/flysystem (PHP) that allows attackers to bypass file extension checks using Unicode RLO characters, potentially leading to remote code execution via malicious file uploads. The main exploit script (CVE-2021-32708_exploit.py) uploads a user-supplied PHP payload disguised as a .txt file using a Unicode RLO character, targeting a /upload.php endpoint and attempting to access the payload in the /uploads/ directory. The scanner script (CVE-2021-32708_scanner.py) checks if the target is running a vulnerable version of Flysystem by accessing /vendor/composer/installed.json. The repository is structured with two Python scripts (exploit and scanner) and a README.md explaining the vulnerability and exploitation method. The exploit is operational, requiring a vulnerable Flysystem installation and a writable uploads directory with code execution enabled.
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.