WPS Hide Login vulnerabilities: Login Page Disclosure records and where the Login url is set
WPS Hide Login's listing says it lets you change the url of the login form page to anything you want, and record titles filed under it include ones ending "Login Page Disclosure".
Their ranges overlap, so go through each one before reading the Login url, the Redirection url and the list of administrators.
On this page
WPS Hide Login vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 10 records for WPS Hide Login. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 1.9.16.4
Worked out from data retrieved on .
Every affected range listed in this source for WPS Hide Login ends before version 1.9.16.4.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
WPS Hide Login <= 1.9.16.3 - Login Page Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2024-6289
Affected versions- All versions up to and including 1.9.16.3
Patched versions: 1.9.16.4
Update to at least version 1.9.16.4.
WPS Hide Login <= 1.9.15.2 - Login Page Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2024-2473
Affected versions- All versions up to and including 1.9.15.2
Patched versions: 1.9.16
Update to at least version 1.9.16.
WPS Hide Login <= 1.9.11 - Hidden Login Page Location Disclosure
- Published:
- Last updated:
- Severity:
- Low (CVSS 3.7)
- CVE:
- CVE-2023-49748
Affected versions- All versions up to and including 1.9.11
Patched versions: 1.9.12
Update to at least version 1.9.12.
WPS Hide Login <= 1.9.0 - Hidden Login Page Location Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2021-24917
Affected versions- All versions up to and including 1.9.0
Patched versions: 1.9.1
Update to at least version 1.9.1.
WPS Hide Login <= 1.5.4.2 - Hidden Login Page Location Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2020-36710
Affected versions- All versions up to and including 1.5.4.2
Patched versions: 1.5.5
Update to at least version 1.5.5.
Show 5 older recordsHide the older records
WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via 'action=rp'
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2019-15825
Affected versions- All versions up to and including 1.5.2.2
Patched versions: 1.5.3
Update to at least version 1.5.3.
WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via Referer Header
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2019-15826
Affected versions- All versions up to and including 1.5.2.2
Patched versions: 1.5.3
Update to at least version 1.5.3.
WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via 'action=confirmaction'
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2019-15823
Affected versions- All versions before 1.5.3
Patched versions: 1.5.3
Update to at least version 1.5.3.
WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via 'adminhash'
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2019-15824
Affected versions- All versions up to and including 1.5.2.2
Patched versions: 1.5.3
Update to at least version 1.5.3.
WPS Hide Login <= 1.0 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
- CVE:
- CVE-2015-9498
Affected versions- All versions before 1.1
Patched versions: 1.1
Update to at least version 1.1.
Check WPS Hide Login on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What WPS Hide Login changes, and the fields it adds
WPS Hide Login's WordPress.org listing says it lets you change the url of the login form page to anything you want.
It says the plugin does not literally rename or change files in core, nor add rewrite rules, and simply intercepts page requests. It also says the wp-admin directory and wp-login.php page become inaccessible, so you should bookmark or remember the url.
The plugin's own settings text has two fields, "Login url" and "Redirection url". For a multisite network, its own text adds the fields "Networkwide default" and "Redirection url default", with a line saying the default can be overridden by individual sites.
On a single site, count every Administrator among the people who can change these fields. WordPress's roles page says an Administrator has access to all administration features within a single site.
WPS Hide Login security records: disclosure titles and overlapping ranges
Title endings that recur in the history include "Login Page Disclosure" and "Hidden Login Page Location Disclosure".
CVE-2024-6289 has a title ending "Login Page Disclosure" (affected: all versions up to and including 1.9.16.3; patched: 1.9.16.4). CVE-2023-49748 has a title ending "Hidden Login Page Location Disclosure" (affected: all versions up to and including 1.9.11; patched: 1.9.12).
Some titles carry a version that differs from the fields. CVE-2015-9498, whose title ends "Cross-Site Request Forgery" and which the source data rates High (CVSS 8.8), has "<= 1.0" in its title, while its affected versions field reads all versions before 1.1, with 1.1 patched.
CVE-2019-15823, whose title ends "Login Page Disclosure via 'action=confirmaction'", has "<= 1.5.2.2" in its title and all versions before 1.5.3 in its field, with 1.5.3 patched. Match on the fields.
Read the ranges together. CVE-2024-2473, whose title also ends "Login Page Disclosure", lists 1.9.16 as patched, and 1.9.16 sits within the range of CVE-2024-6289. Its own range, all versions up to and including 1.9.15.2, takes in 1.9.12, the patched version for CVE-2023-49748.
Reaching one record's patched version can leave a site inside a later record's range, so set the installed version against each range in turn, and read the update guidance at the top of the history after that.
On WPS Hide Login's WordPress.org listing, some changelog entries begin "Fix vulnerability" or "Fix security": read those beside the history on this page.
Four read-only checks: version, login address, redirect and administrators
Work only on a site you are authorised to review, and treat every step as reading: leave each screen without saving.
Ask the site owner for the custom login address rather than looking for it.
Installed version and update status
On the Plugins screen, copy the version from the WPS Hide Login row: WordPress's documentation for that screen lists the version in the Description column. The same page says WordPress displays an update notice there when a plugin hosted in the Plugin Directory has a newer version available, so note any notice, and what the row's Automatic update column shows.
The Login url, and where each vendor page puts it
The listing's installation steps say to go back to Settings › WPS Hide Login to change the option. The plugin's network settings text says instead to go to the site's permalink settings, and a changelog entry says the option location changed from permalinks to general. If the first route is missing, look in the general and permalink settings.
Write down the slug in "Login url", and on a network the "Networkwide default" too. The listing says a site using a page caching plugin other than WP Rocket should add the slug of the new login url to the list of pages not to cache. Record which caching plugin is active and whether the slug is on its list.
Where the Redirection url points, and the site's own login links
Read the "Redirection url" field and write down which page it names. The plugin's own description for that field reads "Redirect URL when someone tries to access the wp-login.php page and the wp-admin directory while not logged in." The field is the record, so there is no need to request either address.
Then list the links the site shows for registering or resetting a password, with the address each uses. The listing's FAQ says you have to give the url for registration and lost password, and that there is no redirection via the plugin for the WordPress defaults. The listing's Compatibility section says the plugin does not work with plugins or themes that hardcoded wp-login.php. Note any link that names that file.
Last, in the discussion settings, where the changelog says the plugin added a warning, record whether "Users must be registered and logged in to comment" is ticked. The plugin's warning text says that if that option is checked, the login link will not be hidden on the comment block.
Who can change or undo the login address
Use the filter links just above the user table on the Users screen to list every Administrator, and match each to a named person. On Multisite, WordPress's roles page says only the Super Admin holds capabilities such as install_plugins and edit_plugins. On a network, list the Super Admins too.
The listing says deactivating the plugin brings the site back exactly to the state it was before. Its FAQ gives two routes back in for a forgotten address: reading whl_page in the database, or removing the plugin's folder, logging in through wp-login.php and reinstalling the plugin. Both need database or file access, so add whoever holds hosting, database or file access to the list.
What the WPS Hide Login version leaves unanswered
Setting the installed version against the history cannot tell you the slug saved in "Login url", the page in "Redirection url", whether a caching plugin other than WP Rocket was given the slug, or who can open the database where whl_page is kept.
A match with a record means the site runs a version inside its range; it does not show that anyone made use of it.
On access, a WordPress security audit records whether anyone on the internet can reach the login screen and the admin area, and what restriction, if any, stands in front of them: an address allow list, a password at the web server, a firewall rule or a plugin. If one is in place, it notes whether xmlrpc.php and the REST API are covered as well as the login form.
Frequently asked questions
The ranges differ record by record: CVE-2024-6289 lists all versions up to and including 1.9.16.3 (patched: 1.9.16.4), and CVE-2015-9498 lists all versions before 1.1 (patched: 1.1). One record's patched version can sit inside another record's range, so work through every record in the history on this page first, then turn to the update guidance at the top of the history.
The records here are the ones the source data files under the slug wps-hide-login, and being filed there does not settle whether a record also applies to Rename wp-login.php. The changelog on the listing describes the initial version as "a fork of the Rename wp-login.php plugin". The plugin's own text has a message that it could not be activated because Rename wp-login.php was already active.
The listing's FAQ says to look for the value of whl_page in the options table, and that on a multisite install it will be in the sitemeta table if the options table has no such option. Its other route, removing the plugin's folder, changes the site, so on a site you are reviewing, ask the owner.
The listing says the plugin works with multisite, with subdomains and subfolders, and that activating it for a network allows you to set a networkwide default while individual sites can still rename their login page to something else. A review of a network records the "Networkwide default" and each site's own "Login url".
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- WPS Hide Login <= 1.9.16.3 - Login Page Disclosure (CVE-2024-6289)
- WPS Hide Login <= 1.9.15.2 - Login Page Disclosure (CVE-2024-2473)
- WPS Hide Login <= 1.9.11 - Hidden Login Page Location Disclosure (CVE-2023-49748)
- WPS Hide Login <= 1.9.0 - Hidden Login Page Location Disclosure (CVE-2021-24917)
- WPS Hide Login <= 1.5.4.2 - Hidden Login Page Location Disclosure (CVE-2020-36710)
- WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via 'action=rp' (CVE-2019-15825)
- WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via Referer Header (CVE-2019-15826)
- WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via 'action=confirmaction' (CVE-2019-15823)
- WPS Hide Login <= 1.5.2.2 - Login Page Disclosure via 'adminhash' (CVE-2019-15824)
- WPS Hide Login <= 1.0 - Cross-Site Request Forgery (CVE-2015-9498)