Loading vulnerability…
CVE-2025-68001 is an Unrestricted Upload of File with Dangerous Type vulnerability in the garidium g-FFL Checkout (g-ffl-checkout) component affecting versions through <= 2.1.0. The upload handling does not sufficiently restrict dangerous file types, enabling an attacker to upload a server-executable payload (e.g., a web shell) to the web server and subsequently invoke it to execute code in the context of the web server/application.
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 is a small standalone exploit project with 3 files: a Python exploit script (CVE-2025-68001.py), a README, and a license. The exploit targets CVE-2025-68001, described as an unauthenticated arbitrary file upload in the WordPress g-FFL Checkout plugin. The script is not part of a larger framework and is designed for interactive bulk exploitation with multithreading. The main exploit flow is: read target URLs from a local file, request each target's /checkout page, extract a checkout_nonce from inline JavaScript using regex, then submit a file upload to the WordPress AJAX handler at /wp-admin/admin-ajax.php using the action ffl_upload_document. The uploaded file is operator-provided, with shell.php as the default. The script then parses the JSON response to recover the stored file path and unique filename, and records successful results to success_results.txt. The README indicates the intended outcome is deployment of a PHP web shell for RCE. Code structure in the Python file includes UI/banner helpers, interactive input functions, target file reading, result writing, checkout reachability testing, nonce extraction, worker/thread orchestration, and a main entrypoint guarded by if __name__ == '__main__'. It uses requests for HTTP operations, threading and Queue for concurrency, and rich for terminal presentation. Overall, this is an operational exploit for unauthenticated web-based file upload leading to remote code execution, rather than a scanner or detection-only script.
1 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.