CVE-2024-31424
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 · uneditedCross-Site Request Forgery (CSRF) 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 · high confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the Login with phone number WordPress plugin (versions <= 1.6.93). The plugin fails to properly validate anti-CSRF tokens (nonces) on its login forms and/or AJAX endpoints, allowing attackers to trick authenticated users into performing unwanted actions such as unauthorized account changes or login operations.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the Login with phone number plugin is installedAccess the WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Login with phone number' or look for a plugin with phone login functionalityAffected if The plugin appears in the list of installed plugins
-
Determine the installed plugin versionIn the Plugins list view, look for the version number displayed under the plugin name, or open the main plugin file (typically named login-with-phone-number.php or similar in wp-content/plugins/) and check the Version header in the plugin comment blockAffected if The displayed version is 1.6.93 or lower, or cannot be determined (older version)
-
Verify if the plugin handles login forms or AJAX requestsCheck the plugin settings in WordPress admin under the plugin menu, or inspect the frontend login page to see if a phone number login form is active and in useAffected if The phone number login form is enabled and accessible to users
-
Confirm absence of nonce validation in plugin codeIf you have code access, review the plugin PHP files for form handlers and AJAX endpoints, looking for calls to wp_verify_nonce, check_admin_referer, or wp_create_nonce; if code access is unavailable, this step requires manual testing or code reviewAffected if No nonce verification is found before processing login or account change requests, or the plugin has not been updated since version 1.6.93
If the Login with phone number plugin is installed at version 1.6.93 or lower and handles login forms or AJAX requests, the environment is likely affected by this CSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all forms and AJAX handlers within the plugin, and verify these nonces using check_admin_referer or wp_verify_nonce before processing any requests.
Latest version of Login with phone number plugin (version > 1.6.93)
- Check the WordPress admin panel for available plugin updates
- Navigate to Plugins > All Plugins > Login with phone number
- Update the plugin to the latest available version (after 1.6.93)
- Verify the update completes successfully
- Test the login functionality to confirm the plugin still works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31424 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-31424 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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