Loading vulnerability…
Gravity Forms for WordPress versions before 2.9.23.1 insufficiently restrict dangerous file types submitted through its chunked-upload functionality. An attacker can upload a PHP file to an affected site and execute it remotely if they can discover or enumerate the resulting upload path.
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.
Repository contains a single Python exploit script and a minimal README. The main file, CVE-2025-13407.py, is a standalone interactive exploit targeting Gravity Forms unauthenticated arbitrary file upload/RCE (claimed as CVE-2025-13407) for versions below 2.9.23.1. The script uses requests and BeautifulSoup to retrieve a target page, parse HTML, locate a Gravity Forms multi-file upload widget via the '.gform_fileupload_multifile' selector, derive form/field identifiers, and drive the upload workflow. Based on the visible code and README, its purpose is not merely detection: it attempts to upload a PHP payload that functions as a mini uploader, enabling follow-on file uploads to the compromised host. The script supports both single-target and multi-target scanning, includes threading for bulk exploitation, disables TLS verification warnings, and logs successful compromises to pwned.txt. The repository is small, operational, and focused on exploitation rather than research or detection.
5 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.