dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-32832

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-31
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 Hamid Alinia Login with phone number login-with-phone-number.This issue affects Login with phone number: from n/a through <= 1.6.93.

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 Login with phone number plugin allows attackers to bypass access controls. The CVSS 9.8 indicates unauthenticated attackers can likely access sensitive authentication functionality without proper authorization checks.

MitigationUpdate to a version beyond 1.6.93 if available, or implement proper authorization checks on all login-related endpoints to verify user identity before granting access.

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 Login with phone number plugin is installed
    Check your CMS/plugin directory for the Login with phone number plugin. For WordPress, check wp-content/plugins/ for a folder related to phone login/phone authentication. For other platforms, locate the plugin/module in the application structure.
    Affected if The plugin is present in the system
  2. Determine the installed plugin version
    Check the plugin's main file header (e.g., readme.txt, plugin.php, or composer.json) for the version number. In WordPress, this is often in the plugin's main PHP file comments or in the Plugins admin page.
    Affected if The version is 1.6.93 or lower, or the version cannot be determined (unknown versions should be treated as affected)
  3. Inspect login endpoints for authorization controls
    Examine the login-related API endpoints or form handlers in the plugin code. Look for functions handling phone number login verification. Check if these endpoints include authorization checks (e.g., capability checks, session validation) before processing login requests.
    Affected if No authorization checks are found before processing authentication requests
  4. Test unauthenticated access to login functions
    If safe to do in a test environment, send a crafted request to the phone login endpoint without providing valid authentication credentials. Observe if the system processes the request without rejecting it.
    Affected if The system accepts and processes unauthenticated requests to login functionality
  5. Review plugin configuration for access restrictions
    Check the plugin admin settings panel for any access control or authorization options. Verify if there are settings to restrict which users/roles can use the phone login feature.
    Affected if No access restrictions are configurable or enabled, allowing any user to access login functionality

A user is affected if the Login with phone number plugin is installed with version 1.6.93 or lower and login endpoints lack proper authorization checks before processing requests.

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 to a version beyond 1.6.93 if available, or implement proper authorization checks on all login-related endpoints to verify user identity before granting access.

Recommended fix Moderate confidence

Update to the latest available version of Login with phone number plugin (version 1.6.94 or later)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Login with phone number' plugin by Hamid Alinia
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin is functioning correctly by testing the phone number login functionality

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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