Classified Listing - Mobile Number Verification <= 1.6.0 - Unauthenticated Authentication Bypass via Firebase OTP Login
Strategic Overview
- Status
- Patched in 1.7.0
- Affected Plugin
- Classified Listing - Mobile Number Verification
- Affected Version
<= 1.6.0- CVSS
- 8.1High
- Weakness type
- CWE-289 · Authentication Bypass by Alternate Name
- CVE
CVE-2026-15985
At a glance
CVE-2026-15985 is a high-severity Authentication Bypass by Alternate Name vulnerability in the Classified Listing - Mobile Number Verification WordPress plugin, affecting versions <= 1.6.0. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7.0; sites on affected versions should update now. Disclosed August 2026, reported by Rafie Muhammad.
Vulnerability Overview
The Classified Listing - Mobile Number Verification plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.6.0. This is due to missing server-side Firebase OTP validation in the process_otp_login() function. This makes it possible for unauthenticated attackers to authenticate as any user with a phone number registered in the plugin's phone table by submitting an arbitrary OTP code and UID through the Firebase OTP login flow. Successful exploitation requires OTP login to be enabled with Firebase selected as the verification gateway, and requires the attacker to know or guess the target account's registered phone number. Administrator account takeover is possible if an administrator account has a phone number registered in the plugin.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-289: Authentication Bypass by Alternate Name
Classified Listing - Mobile Number Verification <= 1.6.0 carries this weakness at process_otp_login(), and reaching it takes no account at all. Authentication bypass by alternate name means access checks are performed against one form of an identifier while the sensitive operation uses another, so a differently spelled value slips through.
Registering or supplying a variant spelling of a privileged account's identifier is enough to be treated as that account. For Classified Listing - Mobile Number Verification the fix is 1.7.0: builds <= 1.6.0 are affected, anything from 1.7.0 onward is not.
Remediation
Update to version 1.7.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Classified Listing - Mobile Number Verification 1.7.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C