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

CVE-2024-30462

HIGH · 8.8 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 1.3.5.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-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.5.1.

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

Cross-Site Request Forgery (CSRF) vulnerability in the HUSKY – Products Filter for WooCommerce plugin allows attackers to trick authenticated administrators into performing unintended state-changing actions (such as modifying plugin settings) by crafting malicious requests that the victim's browser automatically submits.

MitigationUpdate the plugin to a version beyond 1.3.5.1 where the CSRF protection is implemented, or implement anti-CSRF tokens (nonce validation) on all state-changing endpoints within the plugin.

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.5.2

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
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 checks

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

  1. Check installed plugin version
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'HUSKY - Products Filter Professional For Woocommerce' to view the installed version number. Alternatively, inspect the main plugin file header in wp-content/plugins/woof-h层级/ for the Version definition.
    Affected if The displayed version number is less than 1.3.5.2
  2. Confirm plugin is active
    Verify the HUSKY Products Filter plugin is currently activated in the WordPress plugins list.
    Affected if Plugin is active and version is below 1.3.5.2
  3. Verify administrator access exists
    CSRF attacks require a logged-in administrator with access to plugin settings - confirm at least one administrator account exists that can access the plugin configuration.
    Affected if Administrator accounts with plugin access exist and version is below 1.3.5.2

You are affected if the HUSKY Products Filter Professional For Woocommerce plugin version is below 1.3.5.2 and is currently active on your WordPress site.

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.5.2 or later
Fixed in 1.3.5.2
Interim mitigation

Update the plugin to a version beyond 1.3.5.1 where the CSRF protection is implemented, or implement anti-CSRF tokens (nonce validation) on all state-changing endpoints within the plugin.

Recommended fix High confidence

1.3.5.2

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'HUSKY – Products Filter for WooCommerce' (formerly WOOF).
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.3.5.2 or later.
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository or from the vendor's official source.
  6. 6. After updating, verify the plugin is running version 1.3.5.2 or higher in the Plugins list.
  7. 7. Test critical WooCommerce filtering functionality to ensure the update did not break expected behavior.
Caveat Test filter functionality after upgrade as minor behavioral changes in plugin updates are possible

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30462 — 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-2024-30462 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