CVE-2026-8760
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Login with OTP plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.6. This is due to an incomplete fix for CVE-2024-11178: the rate-limit/lockout check added to `otpl_login_action()` was placed only inside the OTP-generation branch and is never evaluated on the OTP-validation branch, and the generated 6-digit OTP additionally has no expiration. This makes it possible for unauthenticated attackers to brute-force the 900,000-value OTP space for any user account (including administrators) and obtain a valid `wp_set_auth_cookie()` session, leading to full site compromise.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Login with OTP WordPress plugin has an authentication bypass vulnerability where the rate-limit/lockout mechanism was only implemented in the OTP-generation code path but not the OTP-validation path. Combined with OTPs that never expire, attackers can brute-force the full 900,000 possible 6-digit OTP values for any user account to obtain a valid wp_set_auth_cookie() session and fully compromise the site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Login with OTP plugin is installedCheck the WordPress plugins directory (wp-content/plugins) for a folder containing 'login' and 'otp' in the name, or query the wp_options table for option_name containing 'active_plugins' to list all active pluginsAffected if The Login with OTP plugin appears in the installed plugins list
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named login-with-otp.php or similar in the plugin folder) and locate the 'Version' header in the plugin comment block, or check the plugin metadata via WP admin panel under Plugins > Installed PluginsAffected if The installed version is lower than the latest patched version available from the vendor (compare your version against the known affected version range if documented)
-
Confirm rate-limiting is missing on OTP validation endpointReview the PHP code handling the OTP validation/submission process (look for functions processing the submitted OTP code, typically in the main plugin file or an includes/authenticate.php file). Search for rate-limit, throttle, lockout, or failed_attempt counters specifically in the validation code pathAffected if The validation code path contains no rate-limiting, throttling, or account lockout logic (only the OTP generation path has these controls)
-
Verify OTPs do not expire or have no expiration settingExamine the plugin settings in WordPress admin panel under the plugin's settings page, and/or inspect the database wp_options table for OTP-related settings (such as otp_expiry, otp_validity, expiration_time). Also check the OTP generation code for any expiration timestamp logicAffected if OTPs are configured to never expire or no expiration parameter exists in the plugin configuration or code
Your environment is affected if the Login with OTP plugin is installed, lacks rate-limiting on the OTP validation path, and OTPs do not expire, allowing brute-force attacks against the OTP validation endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately update the plugin to the latest version if available, or disable the plugin until a patch is released; implement rate-limiting and OTP expiration on the validation branch as an interim measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8760 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data