Cyberlord92 Miniorange OTP Verification With Firebase vulnerabilities

4 vulnerabilities

Known vulnerabilities in Cyberlord92 Miniorange OTP Verification With Firebase, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

8.1CVE-2025-7665cyberlord92miniorange otp verification with firebase+1
EPSS score
0.37%
The Miniorange OTP Verification with Firebase plugin for WordPress is vulnerable to privilege escalation due to a missing capability check on the 'handle_mofirebase_form_options' function in versions 3.1.0 to 3.6.2. This makes it possible for unauthenticated attackers to update the default role to Administrator. Premium features must be enabled in order to exploit the vulnerability.8.1CVE-2024-9861cyberlord92miniorange otp verification with firebase+2
EPSS score
0.63%
The Miniorange OTP Verification with Firebase plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 3.6.0. This is due to missing validation on the token being supplied during the otp login through the plugin. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they know the phone number associated with that user.9.8CVE-2024-9862cyberlord92miniorange otp verification with firebase+2
EPSS score
0.60%
The Miniorange OTP Verification with Firebase plugin for WordPress is vulnerable to Arbitrary User Password Change in versions up to, and including, 3.6.0. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources, and the user current password check is missing. This makes it possible for unauthenticated attackers to change user passwords and potentially take over administrator accounts.9.8CVE-2024-9863cyberlord92miniorange otp verification with firebase+1
EPSS score
0.60%
The Miniorange OTP Verification with Firebase plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 3.6.0 due to the insecure 'administrator' default value for the 'default_user_role' option. This makes it possible for unauthenticated attackers to register an administrator user even if the registration form is disabled.