Vulnity Security <= 1.4.3 - Unauthenticated Authentication Bypass to Administrator via Exposed Pairing Credentials
Strategic Overview
- Status
- Patched in 1.4.4
- Affected Plugin
- Vulnity Security
- Affected Version
<= 1.4.3- CVSS
- 8.1High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-75903
At a glance
CVE-2026-75903 is a high-severity Improper Authentication vulnerability in the Vulnity Security WordPress plugin, affecting versions <= 1.4.3. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.4; sites on affected versions should update now. Disclosed October 2026, reported by Décio Brandão.
Vulnerability Overview
The Vulnity Security plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.4.3 This is due to insufficient protection of the delegated-login pairing credential file on Nginx-based installations, where the plugin's generated server configuration snippet guards the wrong directory path. This makes it possible for unauthenticated attackers to retrieve the stored credentials, forge signed REST API requests, and log in as an administrator.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
Reaching this weakness in Vulnity Security <= 1.4.3 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Vulnity Security the fix is 1.4.4: builds <= 1.4.3 are affected, anything from 1.4.4 onward is not.
Remediation
Update to version 1.4.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Vulnity Security 1.4.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