Winston AI <= 0.0.3 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Settings Deletion
Strategic Overview
- Status
- Patched in 0.0.4
- Affected Version
<= 0.0.3- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1981
At a glance
CVE-2026-1981 is a medium-severity Missing Authorization vulnerability in the HUMN-1 AI Website Scanner & Human Certification by Winston AI WordPress plugin, affecting versions <= 0.0.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.0.4; sites on affected versions should update now. Disclosed March 2026, reported by Legion Hunter.
Vulnerability Overview
The HUMN-1 AI Website Scanner & Human Certification by Winston AI plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the winston_disconnect() function in all versions up to, and including, 0.0.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the plugin's API connection settings via the 'winston_disconnect' AJAX action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
HUMN-1 AI Website Scanner & Human Certification by Winston AI <= 0.0.3 carries this weakness at winston_disconnect, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For HUMN-1 AI Website Scanner & Human Certification by Winston AI the fix is 0.0.4: builds <= 0.0.3 are affected, anything from 0.0.4 onward is not.
Remediation
Update to version 0.0.4, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: HUMN-1 AI Website Scanner & Human Certification by Winston AI 0.0.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C