dbcve.org
Husky Products Filter Professional For WoocommerceWordPress extension · Pluginus

CVE-2023-40334

HIGH · 8.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 1.3.4.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in RealMag777 HUSKY woocommerce-products-filter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects HUSKY: from n/a through <= 1.3.4.2.

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 confidence

A missing authorization vulnerability in the HUSKY woocommerce-products-filter WordPress plugin allows attackers to bypass access control checks and access functionality intended for higher-privileged users due to incorrectly configured security levels.

MitigationUpdate to the patched version of the HUSKY plugin and implement proper role-based authorization checks on all sensitive endpoints and AJAX actions.

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
Affected:< 1.3.4.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the HUSKY products filter plugin is installed
    Check WordPress admin under Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder containing 'husky' or 'products-filter' in the name
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, view the plugin details to see the version number, or check the main plugin PHP file for a Version: header
    Affected if The installed version is less than 1.3.4.3 (for example, 1.3.4.2, 1.3.3.x, or any version below 1.3.4.3)
  3. Identify exposed AJAX actions from the plugin
    Review the plugin PHP files for add_action calls with wp_ajax_ or wp_ajax_nopriv_ hooks, and test accessing these endpoints via wp-admin/admin-ajax.php
    Affected if The plugin exposes AJAX actions that can be accessed by lower-privileged users or unauthenticated attackers without proper capability checks
  4. Check for missing capability checks on sensitive functions
    Review the plugin code for functions performing privileged operations (settings changes, data exports, user data access) and verify if they include current_user_can() or similar authorization checks
    Affected if Sensitive functions lack proper capability or role-based access control checks

The environment is affected if the HUSKY Products Filter plugin version is below 1.3.4.3 and sensitive AJAX actions or functions lack proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.4.3 or later
Fixed in 1.3.4.3
Interim mitigation

Update to the patched version of the HUSKY plugin and implement proper role-based authorization checks on all sensitive endpoints and AJAX actions.

Recommended fix Moderate confidence

1.3.4.3

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Find 'HUSKY - Products Filter Professional for WooCommerce'
  4. 4. Check if current version is below 1.3.4.3
  5. 5. If vulnerable, click 'Update Now' or download version 1.3.4.3 from the WordPress repository/vendor
  6. 6. Verify the update was successful and the new version is 1.3.4.3 or later
  7. 7. Test the product filtering functionality on the frontend to ensure the plugin still works correctly

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-40334 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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