dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-8342

HIGH · 8.1 CVSS v3.1 Published 2025-08-15
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 WooCommerce OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass due to insufficient empty value checking in the lwp_ajax_register function in all versions up to, and including, 1.8.47. This makes it possible for unauthenticated attackers to bypass OTP verification and gain administrative access to any user account with a configured phone number by exploiting improper Firebase API error handling when the Firebase API key is not configured.

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 plugin fails to properly validate empty values in the lwp_ajax_register function and improperly handles Firebase API errors when the API key is not configured, allowing unauthenticated attackers to bypass OTP verification entirely and gain administrative access to any user account with a phone number on file.

MitigationUpdate the plugin to version 1.8.48 or later which addresses the insufficient empty value checking and proper Firebase API error handling; alternatively, ensure a valid Firebase API key is configured if an update is not immediately possible.

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 vulnerable plugin
    Search your WordPress wp-content/plugins directory for a plugin containing the function 'lwp_ajax_register' in its PHP files. Common related terms include 'phone login', 'mobile login', 'firebase', or 'otp' in the plugin name or description.
    Affected if The plugin containing lwp_ajax_register is installed and active.
  2. Check the installed plugin version
    Locate the main plugin PHP file and look for a version comment or check the plugin header (Plugin Name, Version) in the file. Compare this version number against the fixed version 1.8.48.
    Affected if The installed version is lower than 1.8.48.
  3. Verify Firebase API key configuration
    Access the plugin settings page in WordPress admin (usually under Settings or the plugin's own menu). Look for Firebase-related configuration fields such as 'Firebase API Key', 'Firebase Auth Domain', or similar. Check if these fields are populated with valid values or left empty.
    Affected if The Firebase API key field is empty or contains an invalid placeholder value.
  4. Confirm the registration endpoint is accessible
    Make a GET request to your site URL with the parameter /?action=lwp_ajax_register or check if the AJAX action 'lwp_ajax_register' is registered via wp_ajax. This can be verified by inspecting network requests when accessing the login/registration page.
    Affected if The lwp_ajax_register endpoint responds and accepts unauthenticated requests.
  5. Check for users with phone numbers on file
    Query your WordPress database: SELECT * FROM wp_usermeta WHERE meta_key LIKE '%phone%' or check the plugin's custom user meta tables if it stores phone data separately. Count the number of users with populated phone number fields.
    Affected if There are user accounts in the system that have phone numbers stored, making them potential targets for account takeover.

You are affected if the plugin with lwp_ajax_register is installed with a version below 1.8.48 AND either the Firebase API key is missing/empty or users with phone numbers exist in the system.

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 version 1.8.48 or later which addresses the insufficient empty value checking and proper Firebase API error handling; alternatively, ensure a valid Firebase API key is configured if an update is not immediately possible.

Recommended fix High confidence

Version 1.8.48 or later from the WordPress plugin repository

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WooCommerce OTP Login With Phone Number, OTP Verification' plugin
  4. If an update is available, click 'Update Now' to upgrade to version 1.8.48 or later
  5. Alternatively, go to Plugins > Add New > Upload Plugin and upload version 1.8.48 or later from the WordPress plugin repository
  6. After updating, verify the version number in the plugins list matches 1.8.48 or higher
  7. Ensure a Firebase API key is properly configured in the plugin settings if phone number login is needed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8342 — 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-8342 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