CVE-2025-10484
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 · uneditedThe Registration & Login with Mobile Phone Number for WooCommerce plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.1. This is due to the plugin not properly verifying a users identity prior to authenticating them via the fma_lwp_set_session_php_fun() function. This makes it possible for unauthenticated attackers to authenticate as any user on the site, including administrators, without a valid password.
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 confidenceThe Registration & Login with Mobile Phone Number for WooCommerce plugin for WordPress contains an authentication bypass vulnerability in the fma_lwp_set_session_php_fun() function. This function fails to properly verify user identity before establishing an authentication session, allowing unauthenticated attackers to authenticate as any existing user (including administrators) without providing valid credentials.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder containing 'mobile-phone' or similar in the name (the plugin is 'Registration & Login with Mobile Phone Number for WooCommerce').Affected if The plugin appears in the installed plugins list.
-
Identify the installed plugin versionIn WordPress admin > Plugins, click on the plugin name to view details, or open the main plugin PHP file and look for a version comment or define statement.Affected if Any version is potentially affected since no patched version range was specified in the CVE.
-
Confirm the vulnerable function existsInspect the plugin files (typically in the main plugin PHP file) and search for the function 'fma_lwp_set_session_php_fun' to verify the vulnerable code is present.Affected if The function exists in the plugin code.
-
Check for unauthorized admin accountsIn WordPress admin > Users, review all accounts with Administrator role. Look for unfamiliar accounts, especially those created recently or with suspicious usernames.Affected if New or unrecognized administrator accounts exist that you did not create.
-
Review authentication logs for anomaliesCheck WordPress audit logs, server access logs, or security plugins for failed login attempts followed by successful sessions as different users, especially as administrator.Affected if Authentication events show successful logins without proper credential validation.
If the plugin is installed and the vulnerable function exists, the site is vulnerable to unauthenticated admin impersonation; check for unauthorized admin accounts as a sign of exploitation.
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 · scopedUpdate the plugin to the latest version as soon as a patch is released. If no patched version is available, disable the plugin immediately to prevent exploitation.
Latest available version of the plugin (greater than 1.3.1)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Registration & Login with Mobile Phone Number for WooCommerce'
- If an update is available, click 'Update Now'
- After updating, verify the version number reflects the latest available version (above 1.3.1)
- Test that the login functionality works correctly for legitimate users
- Confirm that unauthenticated users can no longer bypass authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10484 — 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-2025-10484 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