Skip to main content
VulnerabilityPublished Updated

CVE-2024-9863: Miniorange OTP Verification with Firebase (WordPress plugin) · Incorrect Privilege Assignment

Affects Miniorange OTP Verification with Firebase (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · patch available : patch Miniorange OTP Verification with Firebase (WordPress plugin) as a priority.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
cyberlord92 Miniorange OTP Verification with FirebaseAffected
  • =0
Fixed in–

AI-suggested

A patch is available for this vulnerability. Users of the Miniorange OTP Verification with Firebase plugin should update to the fixed version immediately to prevent exploitation. Since the vulnerability arises from a default configuration, updating the plugin will correct the 'default_user_role' setting and block unauthorized administrator account creation.

Description

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.

References

Community reviews

Loading reviews…