WordPress security changelog
HIGH CVE-2024-11178 Deferred

Login With OTP: Privilege escalation or authentication bypass

Login With OTP is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess.

CVE / CNA score 8.1 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Login With OTP
Plugin slug
otp-login
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Dec 06, 2024
Weakness
CWE-288 — Authentication Bypass Using an Alternate Path or Channel

This CVE was published Dec 06, 2024 and is one of 2 known issues for this plugin.

Update, patch or deactivate.

Update Login With OTP to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Login With OTP plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.4.2. This is due to the plugin generating too weak OTP, and there’s no attempt or time limit. This makes it possible for unauthenticated attackers to generate and brute force the 6-digit numeric OTP that makes it possible to log in as any existing user on the site, such as an administrator, if they have access to the email.

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary and upstream sources