Frontend Login and Registration Blocks <= 1.0.8 - Authenticated (Subscriber+) Privilege Escalation via Password Reset
Strategic Overview
- Status
- Patched in 1.0.9
- Affected Plugin
- Login, Registration and Lost Password Blocks
- Affected Version
<= 1.0.8- CVSS
- 8.8High
- Weakness type
- CWE-620 · Unverified Password Change
- CVE
CVE-2025-3607
At a glance
CVE-2025-3607 is a high-severity Unverified Password Change vulnerability in the Login, Registration and Lost Password Blocks WordPress plugin, affecting versions <= 1.0.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.9; sites on affected versions should update now. Disclosed April 2025, reported by kr0d.
Vulnerability Overview
The Frontend Login and Registration Blocks plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.0.8. This is due to the plugin not properly validating a user's identity prior to updating a password. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-620: Unverified Password Change
Reaching this weakness in Login, Registration and Lost Password Blocks <= 1.0.8 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. For Login, Registration and Lost Password Blocks the fix is 1.0.9: builds <= 1.0.8 are affected, anything from 1.0.9 onward is not.
Remediation
Update to version 1.0.9, or a newer patched version
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. None of that substitutes for the fix: Login, Registration and Lost Password Blocks 1.0.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Login, Registration and Lost Password Blocks
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C