HUSKY settings let Shop Managers include and execute local files
HUSKY before 1.4.1 concatenates a stored setting value into a file-inclusion path without removing directory traversal. A user with the Shop Manager capability can save a crafted path that selects an arbitrary local file; the plugin then includes and executes that file on every front-end request, including requests from unauthenticated visitors. The published record does not disclose the setting name, save action, include function or which writable local files can provide executable content.
- Component
- HUSKY
- Plugin slug
husky- Affected
- < 1.4.1
- Safe version
1.4.1- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update HUSKY to 1.4.1 or later. Review Shop Manager accounts and plugin settings for traversal paths, inspect local and uploaded files for attacker-controlled executable content, rotate secrets accessible to WordPress, and investigate the host if an unauthorized file may have been included.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The HUSKY WordPress plugin before 1.4.1 does not sanitize a stored setting value against directory traversal before concatenating it into a file inclusion path, allowing users with the shop manager capability to cause the inclusion and execution of arbitrary local files, which is then triggered on every front-end request including for unauthenticated visitors.