miniOrange 2FA WordPress plugin vulnerabilities

The miniOrange 2FA WordPress plugin before 6.3.1 and before 19.3 does not scope its second-factor attempt limit to the account being attacked, keying it instead to a client-supplied identifier that can be changed at will. An attacker who already knows a victim's password can make unlimited one-time-passcode guesses and defeat the second factor. A second validation endpoint applies no attempt limit at all.

The miniOrange 2FA WordPress plugin before 6.3.1 and before 19.3 does not require a validated transaction before deleting site options whose names come from unauthenticated request input. Any visitor can delete arbitrary options, which can lock every administrator out of the dashboard or deactivate the miniOrange 2FA plugin before 6.3.1 and before 19.3 on the site.

The miniOrange 2FA WordPress plugin before 6.2.8 does not correctly limit the number of second-factor verification attempts, tracking them against a client-supplied identifier that is reissued on every login, allowing an attacker who already knows a user's password to guess the one-time code without limit and take over the account.

The miniOrange 2FA WordPress plugin before 6.2.7 does not bind the second factor being configured during the pre-login two-factor challenge to the target account's existing factor, allowing an attacker who knows a user's password to rebind that user's second factor to an attacker-controlled destination, complete the challenge, and take over the account, including administrator accounts.