Quick answers
- Is CVE-2026-15985 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15985 being exploited in the wild.
- How severe is CVE-2026-15985?
- High severity, with a CVSS score of 8.1, published 26 August 2026.
- Which products and versions are affected?
- RadiusTheme Classified Listing - Mobile Number Verification up to and including 1.6.0.
- Is there a fix for CVE-2026-15985?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15985 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-15985?
- Check whether you run RadiusTheme Classified Listing - Mobile Number Verification at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the process_otp_login() function due to missing server-side validation of OTP codes submitted via the Firebase OTP login flow. An unauthenticated attacker can submit an arbitrary OTP and UID to authenticate as any registered user, provided they know the target's phone number and OTP login is enabled with Firebase as the verification gateway. Successful exploitation leads to full account takeover, including administrator accounts if an admin has registered a phone number. Exploitation requires knowledge of the victim's phone number but does not require prior authentication or interaction from the victim. A patch is available in version 1.7.0 or later.
Affected products
- RadiusTheme Classified Listing - Mobile Number Verification up to and including 1.6.0
Timeline
- 2026-08-26: disclosed
- 2026-08-04: other: Fixed in version 1.7.0