dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-69052

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Missing Authorization vulnerability in FmeAddons Registration & Login with Mobile Phone Number for WooCommerce registration-login-with-mobile-phone-number allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Registration & Login with Mobile Phone Number for WooCommerce: from n/a through <= 1.3.1.

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 · moderate confidence

Missing Authorization vulnerability in the FmeAddons Registration & Login with Mobile Phone Number for WooCommerce plugin allows attackers to bypass access control checks due to incorrectly configured security levels. The vulnerability enables unauthorized access to registration/login functionality, likely allowing attackers to register accounts, access user data, or escalate privileges without proper authentication. This affects all versions through 1.3.1.

MitigationApply the vendor patch/upgrade to the latest version of the plugin once available. If no patch exists, temporarily disable the plugin or implement server-side access controls (e.g., IP restrictions, additional authentication layer) until a fix is deployed.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 if the vulnerable plugin is installed
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'registration-login-with-mobile-number-for-woocommerce' or similar FmeAddons plugin. In WordPress admin, go to Plugins > Installed Plugins and look for 'Registration & Login with Mobile Phone Number for WooCommerce' by FmeAddons.
    Affected if The plugin is found installed in the WordPress environment
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the FmeAddons mobile login plugin. Click on the plugin name to view details, or inspect the plugin's main PHP file header for the 'Version' comment tag.
    Affected if The installed version is 1.3.1 or any earlier version
  3. Verify if the registration/login functionality is accessible
    Attempt to access the mobile registration endpoint on your site (commonly /?mobile-registration=1 or similar URL patterns used by the plugin). Check if unauthenticated users can reach the registration or login forms without being redirected to a login page.
    Affected if Unauthenticated access to registration/login forms is possible without proper authorization checks
  4. Inspect plugin access control configuration
    In WordPress admin, navigate to the plugin settings page (WooCommerce > Mobile Login or similar). Review any security-related settings such as 'Allow Guest Registration', 'Require Admin Approval', or role assignment options. Check if these controls can be bypassed or are misconfigured.
    Affected if The plugin settings allow unrestricted access or the access controls are ineffective

A user is affected if the FmeAddons Registration & Login with Mobile Phone Number plugin version 1.3.1 or lower is installed and the mobile registration/login functionality is active and accessible without proper authorization validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch/upgrade to the latest version of the plugin once available. If no patch exists, temporarily disable the plugin or implement server-side access controls (e.g., IP restrictions, additional authentication layer) until a fix is deployed.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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