WPOrLogin – Custom Login, Social Login, CAPTCHA & Security < 3.1.0 - Unauthenticated Login URL Settings Modification
Strategic Overview
- Status
- Patched in 3.1.0
- Affected Plugin
- WPOrLogin – Custom Login, Social Login, CAPTCHA & Security
- Affected Version
< 3.1.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-110691
At a glance
CVE-2026-110691 is a medium-severity Missing Authorization vulnerability in the WPOrLogin WordPress plugin, affecting versions < 3.1.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.0; sites on affected versions should update now. Disclosed October 2026, reported by Naoki Kawahigashi.
Vulnerability Overview
The WPOrLogin – Custom Login, Social Login, CAPTCHA & Security plugin for WordPress is vulnerable to Missing Authorization in all versions up to 3.1.0. This is due to direct update_option() calls on the hide-login slug options from raw $_POST data inside an admin_init callback without any capability check or nonce verification. This makes it possible for unauthenticated attackers to modify the hidden login, registration, and password recovery URL slugs, potentially locking administrators out of the login interface.
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.
CWE-862: Missing Authorization
WPOrLogin < 3.1.0 carries this weakness at update_option(), and reaching it takes no account at all. 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 WPOrLogin the fix is 3.1.0: builds < 3.1.0 are affected, anything from 3.1.0 onward is not.
Remediation
Update to version 3.1.0, 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: WPOrLogin 3.1.0 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