CVE-2026-116401: HUSKY WordPress plugin broken access control

CVE-2026-116401 · Severity: high · CVSS 7.5 · Published 2026-10-30

The HUSKY WordPress plugin allows unauthenticated attackers to access pages and perform actions they should not be permitted to do, such as viewing other users' data. This broken access control vulnerability in versions 1.4.6 and earlier could enable attackers to view sensitive information or tamper with content on affected WordPress sites without needing valid credentials.

Vendors: PluginUs.Net.

Quick answers

Is CVE-2026-116401 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-116401 being exploited in the wild.
How severe is CVE-2026-116401?
High severity, with a CVSS score of 7.5, published 30 October 2026.
Which products and versions are affected?
PluginUs.Net HUSKY <= 1.4.6.
Is there a fix for CVE-2026-116401?
Yes: fixed in 1.4.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116401 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-116401?
Check whether you run PluginUs.Net HUSKY at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 1.4.7

Technical details

The vulnerability is a broken access control flaw in the HUSKY WordPress plugin that permits unauthenticated access to restricted functionality. The attack requires only network access with no authentication needed. An attacker can exploit this to access and potentially modify data or perform administrative actions they are not authorized to perform.

Affected products

  • PluginUs.Net HUSKY <= 1.4.6

Timeline

  • 2026-10-30: disclosed
  • 2026-10-30: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.