# CVE-2024-7491: HUSKY – Products Filter Professional for WooCommerce <= 1.3.6.1 - Insecure Direct Object Reference to Unsubscribe

> Authenticated attackers can unsubscribe users from product notifications by brute-forcing keys in the HUSKY WooCommerce plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-cv79-5xmw-3x8r

## What is CVE-2024-7491?

CVE-2024-7491 is a medium-severity missing authorization vulnerability in realmag777 HUSKY – Products Filter Professional for WooCommerce, published on 25 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The HUSKY – Products Filter Professional for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.3.6.1 via the woof_messenger_remove_subscr AJAX action due to missing validation on the 'key' user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to unsubscribe users from a product notification sign-ups, if they can successfully obtain or brute force the key value for users who signed up to receive notifications. This vulnerability requires the plugin's Products Messenger extension to be enabled.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-7491?

It affects 1 product.


Products: Pluginus Husky - Products Filter Professional for Woocommerce.

## How do I fix CVE-2024-7491?

No fix has been published for CVE-2024-7491 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-7491 being exploited?

There is no known exploitation of CVE-2024-7491 in the wild and no public exploit code.

## Other vulnerabilities in realmag777 HUSKY – Products Filter Professional for WooCommerce

- [CVE-2025-1661](https://insights.sbomify.com/CVE-2025-1661/): HUSKY – Products Filter Professional for WooCommerce <= 1.3.6.5 - Unauthenticated Local File Inclusion (critical 9.8)
- [CVE-2024-6457](https://insights.sbomify.com/CVE-2024-6457/): HUSKY - Products Filter Professional for WooCommerce <= 1.3.6 - Unauthenticated Time-Based SQL Injection (critical 9.8)
- [CVE-2023-40010](https://insights.sbomify.com/CVE-2023-40010/): WordPress HUSKY – Products Filter for WooCommerce (formerly WOOF) Plugin <= 1.3.4.2 is vulnerable to SQL Injection (critical 9.3)
- [CVE-2024-43121](https://insights.sbomify.com/CVE-2024-43121/): WordPress HUSKY plugin <= 1.3.6.1 - Privilege Escalation vulnerability (critical 9.1)
- [CVE-2024-32680](https://insights.sbomify.com/CVE-2024-32680/): WordPress HUSKY plugin <= 1.3.5.2 - Remote Code Execution (RCE) vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7491 and fix it if it is affected.

What it is: CVE-2024-7491 is a medium-severity missing authorization vulnerability in realmag777 HUSKY – Products Filter Professional for WooCommerce, published on 25 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7491 in the wild and no public exploit code.

Affected product: realmag777 HUSKY – Products Filter Professional for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7491/ (Markdown: https://insights.sbomify.com/CVE-2024-7491/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7491
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7491
- OSV: https://osv.dev/vulnerability/CVE-2024-7491

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7491/
Summaries are generated and may contain mistakes; the official description above is the record.