The WPOrLogin WordPress plugin before 3.1.0 does not perform a capability check or validate a nonce before updating
Source GCVE Database
Not known to be exploited : upgrade to 3.1.0 soon.
Data as of 28 Oct 2026, 07:27 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 3.1.0
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade WPOrLogin (WordPress plugin) to 3.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WPOrLogin | Affected
| Fixed in
|
AI-suggested
Upgrade the WPOrLogin plugin to version 3.1.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is provided in the available data.
Description
The WPOrLogin WordPress plugin versions before 3.1.0 lack capability checks and nonce validation when updating hidden-login URL settings. This vulnerability allows unauthenticated attackers to change login, registration, and password-recovery slugs, potentially locking out administrators from the login interface.