LoginPress <= 3.3.1 - Cross-Site Request Forgery to Arbitrary Options Update
Strategic Overview
- Status
- Patched in 4.0.0
- Affected Plugin
- LoginPress | wp-login Custom Login Page Customizer
- Affected Version
<= 3.3.1- CVSS
- 7.5High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-1764
At a glance
CVE-2025-1764 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the LoginPress WordPress plugin, affecting versions <= 3.3.1. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.0.0; sites on affected versions should update now. Disclosed March 2025, reported by Carlos Ferreira.
Vulnerability Overview
The LoginPress | wp-login Custom Login Page Customizer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.3.1. This is due to missing or incorrect nonce validation on the 'custom_plugin_set_option' function. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. The 'WPBRIGADE_SDK__DEV_MODE' constant must be set to 'true' to exploit the vulnerability.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
LoginPress <= 3.3.1 carries this weakness at custom_plugin_set_option, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For LoginPress the fix is 4.0.0: builds <= 3.3.1 are affected, anything from 4.0.0 onward is not.
Remediation
Update to version 4.0.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to LoginPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: LoginPress 4.0.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in LoginPress | wp-login Custom Login Page Customizer
- 8.8CVE-2019-15872: LoginPress <= 1.1.15 SQL Injection
CVE-2019-15872 - 6.4LoginPress <= 1.1.15 Stored Cross-SIte Scripting
- 6.3CVE-2019-15871: LoginPress Unauthorized Settings Update
CVE-2019-15871 - 6.1CVE-2022-0347: LoginPress <= 1.5.11 Reflected Cross-Site Scripting
CVE-2022-0347 - 5.3CVE-2022-41839: LoginPress Settings Changes
CVE-2022-41839
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C