Buddypress Force Password Change <= 0.1 - Authenticated (Subscriber+) Account Takeover via Password Update
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Buddypress Force Password Change
- Affected Version
<= 0.1- CVSS
- 4.2Medium
- Weakness type
- CWE-620 · Unverified Password Change
- CVE
CVE-2025-3793
At a glance
CVE-2025-3793 is a medium-severity Unverified Password Change vulnerability in the Buddypress Force Password Change WordPress plugin, affecting versions <= 0.1. It carries a CVSS score of 4.2 (reachable over the network). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2025, reported by kr0d.
Vulnerability Overview
The Buddypress Force Password Change plugin for WordPress is vulnerable to authenticated account takeover due to the plugin not properly validating a user's identity prior to updating their password through the 'bp_force_password_ajax' function in all versions up to, and including, 0.1. This makes it possible for authenticated attackers, with subscriber-level access and above and under certain prerequisites, to change arbitrary user's passwords, including administrators, and leverage that to gain access to their accounts.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-620: Unverified Password Change
Buddypress Force Password Change <= 0.1 carries this weakness at bp_force_password_ajax, and reaching it takes an account at Subscriber level or above. Unverified password change means the password-update path does not require proof that the requester is the account owner.
An attacker who can reach the endpoint takes over the account outright, and the legitimate owner is locked out of it. No fixed build of this plugin is recorded for Buddypress Force Password Change yet, so installs running <= 0.1 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C