Virusdie <= 1.1.7 - Missing Authorization to Authenticated (Subscriber+) API Key Disclosure
Strategic Overview
- Status
- Patched in 1.1.8
- Affected Plugin
- Virusdie | One-click website security
- Affected Version
<= 1.1.7- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-14864
At a glance
CVE-2025-14864 is a medium-severity Missing Authorization vulnerability in the Virusdie WordPress plugin, affecting versions <= 1.1.7. 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 1.1.8; sites on affected versions should update now. Disclosed February 2026, reported by Sushi Com Abacate.
Vulnerability Overview
The Virusdie - One-click website security plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.1.7. This is due to missing capability checks on the `vd_get_apikey` function which is hooked to `wp_ajax_virusdie_apikey`. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve the site's Virusdie API key, which could be used to access the site owner's Virusdie account and potentially compromise site security.
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
Reaching this weakness in Virusdie <= 1.1.7 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 Virusdie the fix is 1.1.8: builds <= 1.1.7 are affected, anything from 1.1.8 onward is not.
Remediation
Update to version 1.1.8, 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: Virusdie 1.1.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Virusdie | One-click website security
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C