dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-1475

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-07
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
The WPCOM Member plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.7.5. This is due to insufficient verification on the 'user_phone' parameter when logging in. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if SMS login is enabled.

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 WPCOM Member WordPress plugin versions up to 1.7.5 contains an authentication bypass vulnerability due to insufficient verification on the 'user_phone' parameter during SMS login. Attackers can exploit this to authenticate as any existing user on the site, including administrators, without knowing credentials.

MitigationUpdate WPCOM Member plugin to version 1.7.6 or later. If immediate update is not possible, disable SMS login functionality and review user accounts for unauthorized administrative 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. Verify WPCOM Member plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'WPCOM Member' in the list, or check the /wp-content/plugins/ directory for the wpcom-member folder
    Affected if Plugin is present on the site
  2. Check installed plugin version
    In WordPress admin, click on the WPCOM Member plugin to view its details, or inspect the main plugin file (usually wpcom-member.php) to find the version declaration in the plugin header comment
    Affected if Version is 1.7.5 or earlier
  3. Confirm SMS login is enabled
    Go to WPCOM Member settings in WordPress admin (typically under Users > SMS Login or the plugin's settings page) and verify if the SMS login feature is active and configured
    Affected if SMS login functionality is enabled and configured with a SMS service provider
  4. Audit user accounts for unauthorized access
    Review all user accounts in WordPress admin (Users > All Users), paying particular attention to any administrator accounts that were not created by known site administrators, and check user registration dates and activity logs
    Affected if Unexpected administrator accounts exist or suspicious user activity is found

A site is affected if it has WPCOM Member plugin version 1.7.5 or earlier with SMS login functionality enabled, as this combination allows unauthenticated attackers to bypass authentication and gain administrative access.

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 WPCOM Member plugin to version 1.7.6 or later. If immediate update is not possible, disable SMS login functionality and review user accounts for unauthorized administrative access.

Recommended fix Moderate confidence

1.7.6 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WPCOM Member plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify that SMS login functionality still works correctly
  6. 6. Test that authentication functions properly with the updated version
  7. 7. Consider reviewing user accounts that have SMS login enabled to ensure no unauthorized access occurred

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.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-1475 — 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-1475 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