Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Wurdey
- Affected Version
<= 1.0.0- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2026-110955
At a glance
CVE-2026-110955 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Wurdey WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2026, reported by Afan.
Vulnerability Overview
The Wurdey plugin for WordPress is vulnerable to Administrator Account Takeover in all versions up to, and including, 1.0.0. This is due to a failure to verify the authenticity of a login request before granting the user a session. This makes it possible for unauthenticated attackers to log in as an administrator by supplying only a known administrator username, without needing any credentials or signature verification. An attacker must know the username of an administrator account on the target site.
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 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-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in Wurdey <= 1.0.0 takes no account at all. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. No fixed build of this plugin is recorded for Wurdey yet, so installs running <= 1.0.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C