Loading vulnerability…
CVE-2025-1661 is a local file inclusion vulnerability in the HUSKY – Products Filter Professional for WooCommerce WordPress plugin affecting all versions up to and including 1.3.6.5. The flaw is exposed through the 'template' parameter of the unauthenticated 'woof_text_search' AJAX action. Due to insufficient validation of user-supplied file paths, an attacker can cause the application to include arbitrary local files on the server. If an included file contains executable PHP code, that code will be executed in the context of the web server. The issue can also be leveraged to read sensitive local files and to bypass intended access restrictions. The provided description indicates that exploitation may also be chained with the inclusion of uploaded files, including nominally safe file types, where server-side parsing or embedded PHP content results in code execution.
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 (2 hidden).
This repository contains a working exploit for CVE-2025-1661, targeting the HUSKY – Products Filter Professional for WooCommerce WordPress plugin (versions <1.3.6.6). The exploit is implemented in Python (exploit.py) and provides both Local File Inclusion (LFI) and Remote Code Execution (RCE) capabilities. The script first checks the plugin version by accessing the plugin's readme.txt file. It then attempts to extract a required nonce from the target site, which is needed to interact with the vulnerable AJAX endpoint. For RCE, the exploit poisons the web server's access log with a PHP payload via the User-Agent header, then uses the vulnerable template parameter to include the log file and execute arbitrary commands. For LFI, it allows reading arbitrary files from the server. The main endpoints targeted are /wp-content/plugins/woocommerce-products-filter/readme.txt (for version check) and /wp-admin/admin-ajax.php (for exploitation). The exploit is operational and requires the attacker to supply a target URL and either a command to execute or a file to read. The repository is structured with a README.md describing the exploit and a single Python script implementing the attack logic.
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.
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.