dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-7665

HIGH · 8.1 CVSS v3.1 Published 2025-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Miniorange OTP Verification with Firebase WordPress plugin versions 3.1.0 to 3.6.2 contains a privilege escalation vulnerability. The 'handle_mofirebase_form_options' function lacks proper authorization/capability checks, allowing unauthenticated attackers to modify plugin settings and set the default user role to Administrator, thereby gaining full admin access. Exploitation requires premium features to be enabled.

MitigationUpdate the plugin to the latest version beyond 3.6.2 as soon as a patch is released. As an interim measure, disable the plugin or ensure premium features are not enabled until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed plugin version
    Navigate to WordPress admin > Plugins > Miniorange OTP Verification with Firebase and note the version number displayed, or read the plugin's main PHP file (usually in wp-content/plugins/miniorange-otp-verification/) to find the version defined in the plugin header.
    Affected if The installed version is 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1, 3.3.0, 3.3.1, 3.4.0, 3.4.1, 3.4.2, 3.5.0, 3.5.1, 3.5.2, 3.6.0, 3.6.1, or 3.6.2 (any version from 3.1.0 through 3.6.2 inclusive).
  2. Determine if premium features are enabled
    Access the plugin settings page in the WordPress admin panel and look for indicators of active premium or licensed features, such as license status, premium module toggles, or Firebase-related configuration options that are only available in the paid version.
    Affected if Premium or licensed features are actively enabled or configured on the site (this condition is required for the vulnerability to be exploitable).
  3. Review Administrator-level user accounts
    Go to WordPress admin > Users and examine all accounts with the Administrator role. Check the account creation dates and email addresses for any that are unexpected, unknown, or were created after the plugin was installed.
    Affected if There are Administrator accounts that you did not create, have suspicious email addresses, or were added during the time this vulnerable plugin version was active on your site.

Your environment is affected if the plugin version is between 3.1.0 and 3.6.2 inclusive AND premium features are enabled, regardless of whether unauthorized admin accounts are currently present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version beyond 3.6.2 as soon as a patch is released. As an interim measure, disable the plugin or ensure premium features are not enabled until the update can be applied.

Recommended fix Moderate confidence

3.6.3 or latest version

  1. 1. Update the Miniorange OTP Verification with Firebase plugin to the latest available version from the WordPress plugin repository.
  2. 2. After updating, verify that the 'handle_mofirebase_form_options' function now includes proper capability checks.
  3. 3. Review user role settings in WordPress admin to ensure no unauthorized administrator accounts were created.
  4. 4. Consider implementing additional access controls as a defensive measure.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7665 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7665 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data