WPCOM Member <= 1.7.16 - Authentication Bypass via Weak OTP
| CVE | CVE-2025-14002 |
|---|---|
| CVSS | 8.1 (High) |
| Publicly Published | December 15, 2025 |
| Last Updated | December 16, 2025 |
| Researcher |
wesley (wcraft)
|
Description
The WPCOM Member plugin for WordPress is vulnerable to authentication bypass via brute force in all versions up to, and including, 1.7.16. This is due to weak OTP (One-Time Password) generation using only 6 numeric digits combined with a 10-minute validity window and no rate limiting on verification attempts. This makes it possible for unauthenticated attackers to brute-force the verification code and authenticate as any user, including administrators, if they know the target's phone number, and the target does not notice or ignores the SMS notification with the OTP.
Learn more about Authentication Bypass vulnerabilities and how to prevent them.
References
Share
Vulnerability Details for WPCOM Member
| Software Type | Plugin |
|---|---|
| Software Slug | wpcom-member (view on wordpress.org) |
| Patched? | Yes |
| Remediation | Update to version 1.7.17, or a newer patched version |
| Affected Version |
|
| Patched Version |
|
Recent vulnerabilities in WPCOM Member
| # | Title | CVE ID | CVSS | Researchers | Date |
|---|---|---|---|---|---|
| 1 | WPCOM Member <= 1.7.14 - Authenticated (Contributor+) Local File Inclusion via Shortcode | CVE-2025-11920 | Naoya Takahashi (nakko) | October 31, 2025 | |
| 2 | WPCOM Member <= 1.7.7 - Authenticated (Contributor+) Local File Inclusion | CVE-2025-39570 | astra.r3verii | April 16, 2025 | |
| 3 | WPCOM Member <= 1.7.6 - Unauthenticated Time-Based SQL Injection | CVE-2025-2221 | wesley (wcraft) | March 13, 2025 | |
| 4 | WPCOM Member <= 1.7.5 - Authentication Bypass via 'user_phone' | CVE-2025-1475 | wesley (wcraft) | March 6, 2025 | |
| 5 | WPCOM Member <= 1.5.4 - Reflected Cross-Site Scripting | CVE-2024-47378 | ardias | September 30, 2024 | |
| 6 | WPCOM Member <= 1.5.2.1 - Unauthenticated Privilege Escalation via User Meta | CVE-2024-7493 | wesley (wcraft) | September 6, 2024 | |
| 7 | Several WordPress.org Plugins <= Various Versions - Injected Backdoor | CVE-2024-6297 | June 24, 2024 |
This record contains material that is subject to copyright.
Copyright 2012-2026 Defiant Inc.
License: Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. Read more.
Copyright 1999-2026 The MITRE Corporation
License: CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. Read more.
Have information to add, or spot any errors? Contact us at wfi-support@wordfence.com so we can make any appropriate adjustments.
Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!
Learn moreWant to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.
The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.
Documentation