FS Registration Password <= 1.0.1 - Unauthenticated Privilege Escalation via Account Takeover
Strategic Overview
- Status
- Patched in 2.0.1
- Affected Plugin
- FS Registration Password
- Affected Version
<= 1.0.1- CVSS
- 9.8Critical
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-15001
At a glance
CVE-2025-15001 is a critical-severity Authorization Bypass Through User-Controlled Key vulnerability in the FS Registration Password WordPress plugin, affecting versions <= 1.0.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.1; sites on affected versions should update now. Disclosed January 2026, reported by Drew Webber (mcdruid).
Vulnerability Overview
The FS Registration Password plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.0.1. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in FS Registration Password <= 1.0.1 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For FS Registration Password the fix is 2.0.1: builds <= 1.0.1 are affected, anything from 2.0.1 onward is not.
Remediation
Update to version 2.0.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: FS Registration Password 2.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C