# CVE-2024-3061: HUSKY – Products Filter Professional for WooCommerce <= 1.3.5.2 - Authenticated (Admin+) Local File Inclusion

> Authenticated administrators can exploit a local file inclusion vulnerability in the HUSKY WooCommerce plugin to execute arbitrary PHP code and read sensitive data.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qvrh-fmm3-7q76

## What is CVE-2024-3061?

CVE-2024-3061 is a high-severity path traversal vulnerability in realmag777 HUSKY – Products Filter Professional for WooCommerce, published on 29 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The HUSKY – Products Filter Professional for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.3.5.2 via the 'type' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Pluginus Husky - Products Filter Professional for Woocommerce.

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

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

## Is CVE-2024-3061 being exploited?

There is no known exploitation of CVE-2024-3061 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-3061 and fix it if it is affected.

What it is: CVE-2024-3061 is a high-severity path traversal vulnerability in realmag777 HUSKY – Products Filter Professional for WooCommerce, published on 29 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3061 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-3061/ (Markdown: https://insights.sbomify.com/CVE-2024-3061/index.md)
```

## Sources

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

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