CVE-2026-8760: WordPress OTP Authentication Bypass
Critical CVSS (9.8) reachable over network.
TL;DR - Login with OTP for WordPress is vulnerable through version 1.6. - Unauthenticated attackers can brute-force a non-expiring six-digit OTP and obtain a valid WordPress session. - No fixed version, public PoC, or confirmed in-the-wild exploitation was identified. - Disable or remove the plugin, or apply a vendor-confirmed fix as soon as one becomes available.
CVE-2026-8760 is a critical WordPress authentication bypass affecting the Login with OTP plugin through version 1.6. The flaw allows unauthenticated attackers to brute-force a non-expiring six-digit one-time password because rate limiting applies to OTP generation but not OTP validation. A successful guess can produce a valid WordPress authentication cookie and enable account takeover.
For related WordPress security guidance, see our coverage of CVE-2026-116231 and CVE-2026-76482.
Are You Affected?
CVE-2026-8760 affects the Login with OTP plugin for WordPress, identified in plugin source references as otp-login. The affected range includes all versions up to and including 1.6. The available vulnerability record does not provide a lower bound, so defenders should treat any installed release at or below 1.6 as affected.
| Field | Details |
|---|---|
| CVE | CVE-2026-8760 |
| Product | Login with OTP for WordPress |
| Affected versions | All versions through and including 1.6 |
| CVSS | 9.8 Critical |
| Attack vector | Network |
| Authentication required | None |
| Privileges required | None |
| User interaction | None indicated |
| Impact | Account takeover, including administrator takeover and possible full site compromise |
| Patch available | No confirmed fixed version identified |
| CISA KEV | Not listed at the time of assessment |
Version 1.6 is affected. Do not treat upgrading to 1.6 as remediation. The available vulnerability data identifies the vulnerable product and behavior but does not identify a fixed release. Until a vendor or plugin repository advisory names a version that corrects the validation path, organizations should disable or remove the plugin where feasible.
The practical exposure is highest on sites where the plugin protects administrator, editor, or other privileged WordPress accounts. A successful attack can result in a valid WordPress authentication cookie, allowing the attacker to operate through normal authenticated functionality rather than continuing to send OTP guesses.
Analyst’s Take: Treat every installed release at or below 1.6 as exposed until a vendor-confirmed fixed version is identified. The absence of a public PoC or CISA KEV listing does not offset the unauthenticated validation path, non-expiring six-digit OTP, and administrator takeover potential.
The Fix, If You’re in a Hurry
There is currently no confirmed fixed version number in the available vulnerability data. The correct remediation is to upgrade to the first vendor or plugin release that explicitly states it fixes CVE-2026-8760.
Do not assume that a release is safe solely because its version is newer than 1.6. Release documentation should confirm that:
- OTP validation is rate-limited.
- OTPs expire or are otherwise bounded against brute force.
- OTPs cannot be reused.
- Lockout controls apply to validation, not only generation.
- Attackers cannot bypass controls by switching request parameters or actions.
If no confirmed fixed release is available, deactivate and remove the plugin. With WP-CLI, administrators can use:
wp plugin deactivate otp-login
wp plugin uninstall otp-login
Use the uninstall command only after confirming that removal will not delete business-critical data or configuration.
If the plugin cannot immediately be removed, apply compensating controls in front of the site. Throttle requests to the plugin’s OTP generation and validation endpoints, restrict administrative access by network allowlist where practical, and block unnecessary public access to the affected workflow. These measures reduce exposure but do not correct the vulnerable code.
After disabling the plugin or installing a confirmed fix:
- Invalidate existing WordPress sessions.
- Review administrator and editor accounts.
- Check for recent password and email changes.
- Review newly installed plugins and themes.
- Inspect scheduled tasks and recently modified PHP files.
- Preserve logs before rotating credentials if compromise is suspected.
- Rebuild trust in administrator accounts where necessary.
Technical Notes: Immediate Mitigation
Check the installed plugin version:
wp plugin get otp-login --field=version
If the command reports 1.6 or an earlier version, treat the site as vulnerable:
wp plugin deactivate otp-login
If a future vendor-confirmed fixed release becomes available, verify the version and update through the approved change process:
wp plugin update otp-login
wp plugin get otp-login --field=version
The update command is not a substitute for confirming the vendor’s fixed version. At the time of this assessment, that version is unknown.
How This Vulnerability Works
The vulnerability is an incomplete remediation of the related OTP issue tracked as CVE-2024-11178. The plugin’s otpl_login_action() function contains separate behavior for generating an OTP and validating a submitted OTP. A rate-limit or lockout check was added to the generation branch, but the same protection is not applied when an attacker submits guesses to the validation branch.
That distinction is security-critical. An attacker does not need to repeatedly request new OTPs if one generated value remains valid. They can target the validation path directly and submit many candidate values without triggering the generation-side lockout.
The generated OTP is six digits and does not expire, leaving an approximately 900,000-value search space according to the vulnerability description.
A successful guess reaches the normal WordPress authentication flow and can cause wp_set_auth_cookie() to issue a valid authentication cookie. The result is not merely disclosure of an OTP or a temporary denial of service. The attacker can become the targeted WordPress user.
If the target is an administrator, the attacker may be able to:
- Install malicious plugins.
- Alter site content.
- Create additional accounts.
- Access sensitive data.
- Modify configuration.
- Execute code through WordPress administrative functionality.
The affected source references point to the tag 1.6 implementation of the OTP login action and associated code paths:
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L361
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L419
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L424
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L427
The security boundary failure is the absence of effective attempt limits on OTP validation, compounded by an OTP that remains usable without an expiration deadline. A proper fix should enforce limits on validation, expire or invalidate OTPs, prevent reuse, and ensure that lockout state cannot be bypassed by changing request parameters or switching between generation and validation actions.
Severity Explained
CVE-2026-8760 has a CVSS base score of 9.8, rated Critical. The supplied NVD response included the score but did not include the complete vector string. The score is consistent with a vulnerability that is remotely reachable, requires no authentication or prior privileges, needs no user interaction, and can have high confidentiality, integrity, and availability impact.
| Component | Assessment |
|---|---|
| Attack vector | Network: the vulnerable login workflow is remotely reachable |
| Attack complexity | The brute-force workflow is technically straightforward |
| Privileges required | None |
| User interaction | None indicated |
| Confidentiality | High potential impact after account takeover |
| Integrity | High potential impact, especially for administrators |
| Availability | High potential impact if an attacker alters, deletes, or disables site functionality |
The exact CVSS vector should be verified against the authoritative NVD record before reproducing it in compliance reports or risk systems.
The score should not be discounted because exploitation requires multiple OTP guesses. The vulnerable validation path is unauthenticated, and the OTP is both short and non-expiring. Account takeover can also convert a login flaw into full site compromise when a privileged account is targeted.
CWE-307, Improper Restriction of Excessive Authentication Attempts, is associated with the issue in the GitHub Advisory Database. That classification accurately describes the missing control on OTP validation, although the non-expiring OTP is also an important contributing design weakness.
Is CVE-2026-8760 Being Exploited?
CVE-2026-8760 was not listed in the CISA Known Exploited Vulnerabilities catalog at the time of assessment. Consequently, there is no CISA-listed date added, remediation due date, required action, or ransomware campaign association for this CVE.
KEV absence does not prove that exploitation is impossible or that no private exploitation has occurred. It means only that CISA had not listed the vulnerability as a known exploited vulnerability in the checked data.
No confirmed in-the-wild exploitation was identified in the supplied sources. A dedicated public proof-of-concept repository or exploit release was also not confirmed. However, the vulnerability description provides enough detail to reproduce the attack conceptually: send repeated unauthenticated OTP candidates to the validation path and continue until the six-digit value is guessed.
Defenders should distinguish between status evidence and technical exploitability. There is no confirmed public PoC or confirmed active exploitation in the available assessment, but the attack does not require sophisticated memory corruption, specialized tooling, or privileged access.
The CVSS 9.8 rating, administrator takeover potential, and straightforward brute-force mechanics justify prioritizing remediation before exploitation is reported.
Detecting the Vulnerability in Your Environment
Start by inventorying WordPress sites and identifying whether otp-login is installed and active:
wp plugin list --fields=name,status,version,update
wp plugin get otp-login --fields=name,status,version
For larger environments, query each site’s document root or management inventory for the plugin directory. Also check:
- Staging systems.
- Backups that may be restored into production.
- Multisite installations.
- Other sites sharing the same hosting account.
A plugin that is inactive on one site may be active on another site.
Detection should focus on repeated OTP validation failures followed by a successful WordPress authentication event. Exact log field names vary by hosting stack and security plugin, and the vulnerable endpoint name may depend on the plugin’s request handling.
Useful indicators include:
- Repeated requests to the plugin’s OTP action or login endpoint from one source.
- Many candidate OTP values submitted for one account.
- A successful login or administrative request immediately afterward.
- Requests originating from unusual countries, networks, or hosting providers.
- Administrative activity shortly after an OTP brute-force sequence.
A generic web-server search can identify likely plugin-related traffic:
grep -Ei 'otp-login|otp|otpl_login_action|wp-login\.php|admin-ajax\.php' \
/var/log/nginx/access.log /var/log/apache2/access.log
This search is intentionally broad. Terms such as otp can produce unrelated matches, so validate candidate events against the request URI, query string, POST logging, response status, source address, and targeted account.
Many web servers do not log POST bodies by default. Therefore, the absence of an OTP value in access logs does not demonstrate that no guessing occurred.
A useful hunting query for a log platform with structured HTTP fields is:
http.request.path:(*otp* OR */wp-login.php OR */wp-admin/admin-ajax.php)
| stats count() as requests,
count_distinct(http.response.status_code) as statuses,
min(@timestamp) as first_seen,
max(@timestamp) as last_seen
by source.ip, user.name, http.request.path
| where requests >= 20
Adapt field names and syntax to the deployed SIEM. Look for bursts over short intervals, repeated failures such as HTTP 401 or application-level login errors, and a subsequent successful response.
A generic access-log pattern worth escalating is:
<SOURCE_IP> - - [timestamp] "POST <OTP_OR_LOGIN_PATH> HTTP/1.1" 401
<SOURCE_IP> - - [timestamp] "POST <OTP_OR_LOGIN_PATH> HTTP/1.1" 401
<SOURCE_IP> - - [timestamp] "POST <OTP_OR_LOGIN_PATH> HTTP/1.1" 200
<SOURCE_IP> - - [timestamp] "GET /wp-admin/ HTTP/1.1" 200
This pattern is illustrative rather than a vendor-specific signature. A successful HTTP response alone does not prove authentication, and some applications return HTTP 200 for failed login attempts. Correlate web logs with WordPress, reverse-proxy, WAF, and security-plugin telemetry.
After remediation, review for post-authentication activity. Prioritize changes to:
wp_usersandwp_usermeta.- Administrator membership.
- Plugin and theme installation.
- The
active_pluginsoption. wp-config.php.- Unexpected PHP files.
- New cron jobs.
- Outbound requests from the web process.
Invalidate all existing sessions where possible, because a previously issued authentication cookie may remain usable after the plugin is disabled.
Recommended Response Checklist
Use this checklist for affected sites:
- [ ] Confirm whether
otp-loginis installed. - [ ] Confirm the installed version.
- [ ] Treat version 1.6 and earlier as vulnerable.
- [ ] Disable or remove the plugin if no confirmed fixed version is available.
- [ ] Apply temporary request throttling to OTP validation endpoints.
- [ ] Restrict administrative access where practical.
- [ ] Invalidate existing WordPress sessions.
- [ ] Review administrator accounts and recent account changes.
- [ ] Search logs for repeated OTP validation attempts.
- [ ] Inspect plugins, themes, PHP files, and scheduled tasks.
- [ ] Preserve evidence if compromise is suspected.
- [ ] Monitor vendor communications for a confirmed fix.
References and Further Reading
The primary references supplied for this vulnerability are:
-
NVD reference for the related vulnerability, CVE-2024-11178
https://nvd.nist.gov/vuln/detail/CVE-2024-11178 -
Login with OTP source, tag 1.6, OTP login action
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L361 -
Login with OTP source, related code path
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L419 -
Login with OTP source, related code path
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L424 -
Login with OTP source, related code path
https://plugins.trac.wordpress.org/browser/otp-login/tags/1.6/lib/otpl-class.php#L427 -
GitHub Advisory Database entry
https://github.com/advisories/GHSA-cq2x-2xjr-vm5v
CISA KEV status was checked and returned:
{
"on_kev": false,
"cve_id": "CVE-2026-8760"
}
The absence of a confirmed fixed version is the most important unresolved remediation detail. Site owners should monitor the plugin’s official distribution and vendor communications for a release that explicitly addresses CVE-2026-8760. Until then, disable or remove Login with OTP, apply layered request controls, invalidate existing sessions, and investigate whether the vulnerable login path has been targeted.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.