Rename wp-login.php <= 2.6.0 - Cross-Site Request Forgery & Unauthenticated Settings Change
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Rename wp-login.php
- Affected Version
<= 2.6.0- CVSS
- 6.5Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-1732
At a glance
CVE-2022-1732 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Rename wp-login.php WordPress plugin, affecting versions <= 2.6.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2022, reported by Daniel Ruf.
Vulnerability Overview
The Rename wp-login.php plugin for WordPress is vulnerable to Cross-Site Request Forgery as well as an authorization bypass vulnerability in versions up to, and including, 2.6.0. This allows unauthenticated attackers to update the site's login page directly or by tricking administrative users into performing an action such as clicking a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Rename wp-login.php <= 2.6.0 takes no account at all. 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. No fixed build of this plugin is recorded for Rename wp-login.php yet, so installs running <= 2.6.0 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?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C