Skip to content
WPJury
No. 00175 WooCommerce

HUSKY: powerful filtering, but not worth the security risk

The verdict HUSKY is feature-rich and can handle complex WooCommerce catalogs, but it is not worth choosing for a new store today. Its history of serious security vulnerabilities, recurring compatibility problems, and a steep configuration experience outweigh the benefits unless you are maintaining an existing site that already depends on it and can enforce rapid updates and staging tests.
Not recommended The ruling
Get v3.4.3

via WorldPressIT · complete package

Best for
  • legacy WooCommerce stores already using WOOF
  • large catalogs with complex attributes
  • developers comfortable with shortcodes and debugging
  • stores using Divi or WPML
Skip it if
  • security-sensitive ecommerce stores
  • site owners wanting simple setup
  • stores relying heavily on page builders
  • teams that cannot test plugin updates
Version 3.4.3 Updated 12 Sep 2026 Licence GPL

HUSKY, formerly known as WOOF, is a WooCommerce product-filter plugin built for stores where the default catalog controls are not enough. It can filter by categories, attributes, tags, price, SKU, text, custom metadata, ACF fields and product taxonomies. It can also display filters as checkboxes, radio buttons, dropdowns, sliders, colors, images and labels. AJAX filtering, product-count updates, shortcode-based product grids, saved searches and a step-by-step product wizard give it an unusually broad feature set.

That breadth is HUSKY’s real strength. For a catalog with thousands of products, several attribute systems and unusual filtering requirements, it gives developers many ways to construct a search interface without writing every query from scratch. The free WordPress.org version documents AJAX filtering, price ranges, SKU search and a Turbo Mode intended to avoid generating large MySQL queries. It also documents compatibility with WPML, Divi and PHP 7.4 through PHP 8.x. The plugin’s shortcode and API approach can be useful when a standard sidebar widget is too limiting.

HUSKY is less convincing as a polished store-owner tool. The settings are extensive rather than intuitive, and important behaviour depends on the theme’s product-loop markup, the selected comparison logic and whether the filter is operating in AJAX, redirect or Turbo Mode. The plugin itself says AJAX works with roughly 95% of WordPress themes and should be tested before production. That is a useful warning: the remaining compatibility cases are exactly the ones that can cause broken pagination, incorrect product counts, filters that disappear on mobile, or results that fail to update.

The support forum shows recurring reports about category context being lost, price sliders showing irrelevant ranges, filters failing after WooCommerce updates, mobile display problems and custom Elementor or Divi layouts not behaving as expected. Several issues are resolved through configuration changes, but that still means the plugin demands testing and troubleshooting rather than simply being installed and forgotten. User reviews are broadly positive, with strong praise for support, yet the reviews also include complaints about complexity and the plugin overriding custom product-collection behaviour.

The larger problem is security. NVD records CVE-2025-1661, a critical unauthenticated local-file-inclusion vulnerability affecting HUSKY versions through 1.3.6.5. Wordfence’s vulnerability record later lists additional issues, including unauthenticated SQL injection through version 1.3.7.1 and authenticated object-reference problems through version 1.3.7.3. The current version must be checked directly before use, but this pattern is enough to make HUSKY a poor default recommendation for a new production store.

Compared with FacetWP, HUSKY offers more WooCommerce-specific controls and a free starting point, while FacetWP is more structured, developer-focused and built around an indexing system; its Basic plan is documented at $99 per year. Filter Everything is the more obvious alternative for stores wanting URL-friendly filtering that works across themes and page builders with less reliance on custom markup. WooCommerce’s own Product Filters extension is also a safer fit when a store can accept a narrower feature set and prefers official WooCommerce documentation and support channels.

Verdict: HUSKY can solve difficult filtering requirements, but new stores should choose a better-maintained alternative. Keep it only on an existing installation where its features are already embedded, updates are monitored, and every change is tested on staging.

Questions people ask

Is HUSKY a good WooCommerce filter plugin?
It is powerful, but it is not a good default choice for a new store. The feature set is strong, while the security history and compatibility troubleshooting create too much operational risk.
Does HUSKY support AJAX filtering?
Yes. HUSKY supports optional AJAX filtering, dynamic product counts and Turbo Mode, but the developer warns that AJAX behaviour depends on the active theme and should be tested before launch.
What is the difference between HUSKY and WOOF?
They are the same product under different names. HUSKY is the newer name for the plugin formerly marketed as WOOF WooCommerce Products Filter.
Has HUSKY had security vulnerabilities?
Yes. CVE-2025-1661 affected versions through 1.3.6.5 with a critical unauthenticated local-file-inclusion issue, and later vulnerability records list additional problems in subsequent releases. Use only a verified current version and update promptly.
Is FacetWP better than HUSKY?
For most new projects, yes. FacetWP is more predictable for developers and uses an indexing approach, although it costs more and may require more deliberate setup for WooCommerce-specific layouts.

Get HUSKY: powerful filtering, but not worth the security risk 3.4.3

Complete package, ready to install, via WorldPressIT.

Download

Other rulings

WooCommerce Stripe Gateway: worth using, but not version 4.9.0 Yes, the official WooCommerce Stripe Gateway is worth using for most stores that already rely on Stripe, especially if you want cards, wallets, local payment methods, subscriptions, and express checkout in one integration. But the supplied 4.9.0 build is not worth installing: the official plugin has moved on to the 11.x series, so use the current release instead of an outdated package. Situational Amiy: worth it for a beauty shop, not a lean WooCommerce build Amiy is worth considering if you need a beauty-focused WooCommerce storefront that can be assembled quickly with Elementor and imported demo content. It is not the best choice for a lightweight, Gutenberg-first site or a store that needs unusually clean documentation and effortless customization. Situational WooCommerce Royal Mail: worth it for UK rate calculation, not fulfilment WooCommerce Royal Mail is worth paying for if you run a UK-based store and need Royal Mail rates calculated at checkout without building an API integration. It is not a complete shipping system: label creation, tracking imports, and Click & Drop workflows remain separate, so high-volume stores may get better value from PluginHive or a shipping platform. Situational Kirema: worth it for an Elementor furniture store, but not a complete shop solution Kirema is worth considering if you already use Elementor Pro and want a polished furniture-store starting point rather than designing WooCommerce templates from scratch. It is not worth buying for beginners expecting a complete theme, built-in functionality, or a cheaper alternative to Elementor Pro. Situational