Summary
CVE-2026-92969 is an unauthenticated Local File Inclusion (LFI) vulnerability in the HUSKY – Products Filter for WooCommerce Professional WordPress plugin, affecting all versions up to and including 1.4.4. The flaw allows attackers to include and execute arbitrary .php files on the server without any credentials, resulting in a CVSS v3.1 score of 8.1 (High).
Technical details
- Root cause: The plugin’s
woof_draw_productsAJAX handler processes acustom_tplshortcode attribute without properly validating or sanitizing the supplied filename before passing it to a PHP include/require statement (CWE-98). - Access control weakness: The only protection on this AJAX endpoint is a nonce check against
woof_front_nonce. This nonce is emitted in plaintext inline JavaScript on every public-facing page of the site, so any unauthenticated visitor can retrieve and reuse it to reach the vulnerable code path. - Trigger conditions: An attacker sends a crafted request to the plugin’s front-end AJAX action with a manipulated
custom_tpl/shortcode value pointing to an attacker-controlled or otherwise accessible.phpfile. - Attack vector: Network — no authentication or user interaction required.
- Impact: Arbitrary PHP file inclusion can lead to execution of malicious code (e.g., in files placed via upload functionality or found elsewhere on the server), bypass of access controls, disclosure of sensitive data, and full compromise of the affected WordPress site depending on server configuration.
Affected software
- HUSKY – Products Filter for WooCommerce Professional (realmag777 / pluginus, formerly WOOF) — all versions up to and including 1.4.4
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update HUSKY – Products Filter for WooCommerce Professional to version 1.4.5 or later, which resolves this vulnerability.
- If patching is not immediately possible: Restrict or disable public access to the plugin’s front-end AJAX filter functionality (e.g., via a web application firewall rule blocking requests containing suspicious
custom_tpl/shortcode path traversal patterns), and monitor server logs for unexpected.phpfile inclusion attempts. Review the server for any unauthorized or unexpectedly uploaded.phpfiles.

