HUSKY - Security Vulnerability (CVE-2026-92969)

CVE-2026-92969

Vulnerability CVE-2026-92969 PLUGIN husky HIGH

The HUSKY – Products Filter for WooCommerce Professional plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.4.4 via the 'shortcode' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php 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 .php file types can be uploaded and included. This vulnerability is exploitable by unauthenticated users because the only access control is a nonce check against woof_front_nonce, which is publicly emitted into inline JavaScript on every front-end page and is therefore obtainable by any site visitor without authentication.

CVE-2026-92969

HIGH CVSS 8.1 Published 2026-09-22 Updated 2026-09-22

AI Risk High (87/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent

Severity Band HIGH

CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected Components 2

Reference Links 8

AI Risk Engine High (87/100)

Exploitability Very High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-09-22 CVE published and first recorded in the threat feed.
2026-09-22 Record updated with latest vulnerability metadata.
2026-09-22 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 2 hours ago

AI enriched 2 hours ago (2026-09-22 18:34 UTC)

Technical Summary

Potential Impact

Severity is HIGH (CVSS 8.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Very High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 87/100 (High, Very High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

HUSKY PLUGIN · husky Affected range not specified Fixed version not specified

Woocommerce Products Filter PLUGIN · woocommerce-products-filter Affected range not specified Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update HUSKY to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs HUSKY, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs HUSKY. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update HUSKY to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Path Traversal flaw. An attacker who exploits it can read files outside the intended directory, including wp-config.php.