Custom Login Page Styler <= 7.1.1 - Missing Authorization to Authenticated (Subsciber+) Log Deletion and Session Termination
Strategic Overview
- Status
- Patched in 7.1.2
- Affected Version
<= 7.1.1- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-13530
At a glance
CVE-2024-13530 is a medium-severity Missing Authorization vulnerability in the Login Page Styler WordPress plugin, affecting versions <= 7.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subsciber level or above. The issue is fixed in version 7.1.2; sites on affected versions should update now. Disclosed January 2025, reported by theviper17y.
Vulnerability Overview
The Custom Login Page Styler – Limit Login Attempts – Restrict Content With Login – Redirect After Login – Change Login URL – Sign in , Sign out plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the lps_handle_delete_all_logs(), lps_handle_delete_login_log(), and lps_handle_end_session() functions in all versions up to, and including, 7.1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete login logs and end user sessions.
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.
CWE-862: Missing Authorization
Login Page Styler <= 7.1.1 carries this weakness at lps_handle_delete_all_logs(), and reaching it takes an account at Subsciber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Login Page Styler the fix is 7.1.2: builds <= 7.1.1 are affected, anything from 7.1.2 onward is not.
Remediation
Update to version 7.1.2, 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 Page Styler 7.1.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Login Page Styler – Custom WordPress Login Page Customizer & Security
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C