Focus on wpserveur vulnerabilities and metrics.
Last updated: 08 Mar 2025, 23:25 UTC
This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with wpserveur. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.
For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.
Total wpserveur CVEs: 11
Earliest CVE date: 30 Aug 2019, 13:15 UTC
Latest CVE date: 15 Jul 2024, 06:15 UTC
Latest CVE reference: CVE-2024-6289
30-day Count (Rolling): 0
365-day Count (Rolling): 2
Calendar-based Variation
Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.
Month Variation (Calendar): 0%
Year Variation (Calendar): 100.0%
Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 100.0%
Average CVSS: 4.94
Max CVSS: 7.5
Critical CVEs (≥9): 0
| Range | Count |
|---|---|
| 0.0-3.9 | 3 |
| 4.0-6.9 | 3 |
| 7.0-8.9 | 5 |
| 9.0-10.0 | 0 |
These are the five CVEs with the highest CVSS scores for wpserveur, sorted by severity first and recency.
The WPS Hide Login WordPress plugin before 1.9.16.4 does not prevent redirects to the login page via the auth_redirect WordPress function, allowing an unauthenticated visitor to access the hidden login page.
The WPS Hide Login plugin for WordPress is vulnerable to Login Page Disclosure in all versions up to, and including, 1.9.15.2. This is due to a bypass that is created when the 'action=postpass' parameter is supplied. This makes it possible for attackers to easily discover any login page that may have been hidden by the plugin.
The WPS Hide Login plugin for WordPress is vulnerable to login page disclosure even when the settings of the plugin are set to hide the login page making it possible for unauthenticated attackers to brute force credentials on sites in versions up to, and including, 1.5.4.2.
The WPS Hide Login WordPress plugin before 1.9.1 has a bug which allows to get the secret login page by setting a random referer string and making a request to /wp-admin/options.php as an unauthenticated user.
WPS Hide Login 1.6.1 allows remote attackers to bypass a protection mechanism via post_password.
The wps-hide-login plugin before 1.1 for WordPress has CSRF that affects saving an option value.
The wps-hide-login plugin before 1.5.3 for WordPress has a protection bypass via wp-login.php in the Referer field.
The wps-hide-login plugin before 1.5.3 for WordPress has an action=rp&key&login protection bypass.
The wps-hide-login plugin before 1.5.3 for WordPress has an adminhash protection bypass.
The wps-hide-login plugin before 1.5.3 for WordPress has an action=confirmaction protection bypass.
The wps-child-theme-generator plugin before 1.2 for WordPress has classes/helpers.php directory traversal.