Loading vulnerability…
CVE-2025-32206 is an unrestricted file upload vulnerability in LABCAT Processing Projects affecting versions through 1.0.2. According to the provided description, the application does not adequately restrict upload of dangerous file types, allowing an attacker to upload a web shell to the web server. This indicates insufficient validation or enforcement of allowed file types during file upload handling, resulting in attacker-controlled executable content being placed in a web-accessible or executable server context.
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 Python exploit script (CVE-2025-32206.py) targeting the Processing Projects WordPress plugin (versions <= 1.0.2) for an arbitrary file upload vulnerability (CVE-2025-32206). The exploit requires valid WordPress administrator credentials. It automates the process of logging in, extracting necessary form fields, creating a ZIP archive containing a PHP web shell, uploading it via a vulnerable endpoint, and verifying shell access. The shell allows arbitrary command execution via the 'cmd' parameter. The repository is well-structured, with a single exploit script, a README providing detailed usage and vulnerability information, and a license file. The main attack vector is network-based, exploiting web application endpoints. The exploit is operational, providing a working web shell payload but not integrated into a larger framework.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.