Summary
CVE-2026-15985 is an authentication bypass vulnerability affecting the "Classified Listing – Mobile Number Verification" WordPress plugin by RadiusTheme, in all versions up to and including 1.6.0. The flaw stems from missing server-side validation of Firebase OTP (one-time password) responses in the plugin’s process_otp_login() function, allowing an unauthenticated attacker to log in as an arbitrary existing user. The vulnerability carries a CVSS v3.1 base score of 8.1 (High).
Technical details
- Root cause: The
process_otp_login()function trusts the OTP code and Firebase UID submitted by the client without independently verifying them against Firebase on the server side. - Trigger conditions: The site must have OTP-based login enabled with Firebase configured as the verification/SMS gateway, and the attacker must know the target user’s registered phone number.
- Attack vector: Network-based (remote, unauthenticated). The attacker submits a crafted login request containing an arbitrary OTP code and UID for the victim’s phone number, bypassing the actual OTP verification step.
- Impact: Successful exploitation allows full account takeover of any user whose phone number is known to the attacker, including potentially administrator accounts, resulting in loss of confidentiality, integrity, and availability of the affected WordPress site.
Affected software
- Classified Listing – Mobile Number Verification (RadiusTheme add-on) — versions up to and including 1.6.0
Severity
- CVSS v3.1 Base Score: 8.1 (High)
- Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - CWE-289: Authentication Bypass by Alternate Name
Mitigation and recommended actions
- Immediate: Update the "Classified Listing – Mobile Number Verification" add-on to the latest version available from RadiusTheme that addresses server-side OTP/UID validation against Firebase. Check the vendor’s download page for the current release before applying.
- If no patch is available/applied: Disable Firebase OTP-based login on the site until a verified fix is installed; monitor authentication logs for anomalous logins tied to known phone numbers; consider enforcing multi-factor authentication independent of the vulnerable OTP flow for privileged accounts (administrators, editors).
- Review recent login activity for accounts associated with known/public phone numbers to identify potential prior exploitation.

