Husky Products Filter Professional For WoocommerceWordPress extension · Pluginus
CVE-2023-50861
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in realmag777 HUSKY – Products Filter for WooCommerce (formerly WOOF).This issue affects HUSKY – Products Filter for WooCommerce (formerly WOOF): from n/a through 1.3.4.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the HUSKY – Products Filter for WooCommerce plugin allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Husky Products Filter Professional For WoocommerceWordPress extension
< 1.3.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installation directoryAccess your WordPress site's file system and navigate to /wp-content/plugins/ and look for a folder related to 'woof', 'husky', 'products-filter', or similar. The plugin is distributed by Pluginus.Affected if The plugin directory is not found or does not exist on the server.
-
Read the plugin version from headerIn the plugin directory, open the main PHP file (often named index.php, woof.php, or similar) and locate the version string in the plugin header comment (e.g., 'Version: 1.3.4.3').Affected if The version line cannot be found or returns no version information.
-
Compare installed version to vulnerable rangeCompare the version you found in step 2 against the affected range: any version lower than 1.3.4.4 is vulnerable.Affected if The installed version is less than 1.3.4.4 (e.g., 1.3.4.3, 1.3.4.2, 1.3.3.x, etc.).
-
Check if plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify whether the HUSKY Products Filter plugin is activated.Affected if The plugin is active and the version is below 1.3.4.4.
You are affected if the HUSKY Products Filter for WooCommerce plugin is installed, active, and running a version lower than 1.3.4.4.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.4.4
Implement anti-CSRF tokens (nonces) for state-changing operations and validate request origin via Referer header checks or SameSite cookie attributes.
1.3.4.4
- Update the HUSKY – Products Filter for WooCommerce plugin to version 1.3.4.4 or later via the WordPress plugin dashboard, or replace the plugin files with the updated version from the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Husky Products Filter Professional For Woocommerce
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50861 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data