HomeWordPress vulnerabilitiesHide My WP Ghost
Hide My WP Ghost vulnerabilities
Hide My WP Ghost has 11 known vulnerabilities in this database. The most recent published record is dated 19 Sep 2026.
- Known vulnerabilities
- 11
- Active installs
- 100,000+
- Latest version
- 7.0.12
- Last updated
- 29 Sep 2026
- Most recent
- 19 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Open redirect CVE-2026-7527 | Medium 4.7 | Up to 7.0.02 | Fixed in a later version (latest 7.0.12) | 19 Sep 2026 |
| Security weakness CVE-2026-86796 | Medium 5.3 | Before 7.0.11 | Fixed in 7.0.11 | 18 Sep 2026 |
| Security weakness CVE-2026-86800 | Medium 5.3 | Before 7.0.11 | Fixed in 7.0.11 | 18 Sep 2026 |
| Path traversal CVE-2025-2056 | High 7.5 | Before 5.4.02 | Fixed in 5.4.02 | 14 Mar 2025 |
| Cross-site scripting (XSS) CVE-2024-10825 | Medium 6.1 | Before 5.3.02 | Fixed in 5.3.02 | 15 Nov 2024 |
| Security weakness CVE-2024-6420 | High 8.6 | Before 5.2.02 | Fixed in 5.2.02 | 23 Jul 2024 |
| Security weakness CVE-2023-34001 | Medium 5.3 | Before 5.0.26 | Fixed in 5.0.26 | 4 Jun 2024 |
| Security weakness CVE-2022-4537 | Medium 6.5 | Up to 5.0.18 | Fixed in a later version (latest 7.0.12) | 9 May 2023 |
| SQL injection CVE-2022-4681 | Critical 9.8 | Before 6.2.9 | Fixed in 6.2.9 | 6 Feb 2023 |
| SQL injection CVE-2021-36916 | High 8.6 | Up to 6.2.3 | Fixed in a later version (latest 7.0.12) | 24 Nov 2021 |
| Broken access control CVE-2021-36917 | Medium 6.5 | Up to 6.2.3 | Fixed in a later version (latest 7.0.12) | 24 Nov 2021 |
Read the published descriptions
- CVE-2026-7527, 19 Sep 2026
- The WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 7.0.02. This is due to the plugin not properly validating user input. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into clicking on a specially crafted link. Exploitation requires tricking a logged-in user into clicking a crafted logout URL; the victim is fully logged out via wp_logout() before the malicious redirect is issued, making the logout irreversible as part of the attack chain. CVE record
- CVE-2026-86796, 18 Sep 2026
- The Hide My WP Ghost WordPress plugin before 7.0.11 does not verify that a request is a genuine WooCommerce request before disabling its firewall, threat-detection and login/URL-hiding protections, treating the mere presence of an attacker-suppliable request parameter as sufficient, which allows unauthenticated attackers to disable those protections and re-expose the concealed login and admin URLs on any request. CVE record
- CVE-2026-86800, 18 Sep 2026
- The Hide My WP Ghost WordPress plugin before 7.0.11 does not properly validate a loopback security-check request before disabling its login and URL hiding protection, dropping that protection precisely when the request's verification value is missing or incorrect, which any visitor can arrange, allowing unauthenticated attackers to re-expose the concealed WordPress login page location. CVE record
- CVE-2025-2056, 14 Mar 2025
- The WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 5.4.01 via the showFile function. This makes it possible for unauthenticated attackers to read the contents of specific file types on the server, which can contain sensitive information. CVE record
- CVE-2024-10825, 15 Nov 2024
- The Hide My WP Ghost - Security & Firewall plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the URL in all versions up to, and including, 5.3.01 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrative user into performing an action such as clicking on a link. CVE record
- CVE-2024-6420, 23 Jul 2024
- The Hide My WP Ghost WordPress plugin before 5.2.02 does not prevent redirects to the login page via the auth_redirect WordPress function, allowing an unauthenticated visitor to access the hidden login page. CVE record
- CVE-2023-34001, 4 Jun 2024
- Improper Restriction of Excessive Authentication Attempts vulnerability in WPPlugins - WordPress Security Plugins Hide My WP Ghost allows Functionality Bypass.This issue affects Hide My WP Ghost: from n/a through 5.0.25. CVE record
- CVE-2022-4537, 9 May 2023
- The Hide My WP Ghost - Security Plugin plugin for WordPress is vulnerable to IP Address Spoofing in versions up to, and including, 5.0.18. This is due to insufficient restrictions on where the IP Address information is being retrieved for request logging and login restrictions. Attackers can supply the X-Forwarded-For header with with a different IP Address that will be logged and can be used to bypass settings that may have blocked out an IP address from logging in. CVE record
- CVE-2022-4681, 6 Feb 2023
- The Hide My WP WordPress plugin before 6.2.9 does not properly sanitize and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection. CVE record
- CVE-2021-36916, 24 Nov 2021
- The SQL injection vulnerability in the Hide My WP WordPress plugin (versions <= 6.2.3) is possible because of how the IP address is retrieved and used inside a SQL query. The function "hmwp_get_user_ip" tries to retrieve the IP address from multiple headers, including IP address headers that the user can spoof, such as "X-Forwarded-For." As a result, the malicious payload supplied in one of these IP address headers will be directly inserted into the SQL query, making SQL injection possible. CVE record
- CVE-2021-36917, 24 Nov 2021
- WordPress Hide My WP plugin (versions <= 6.2.3) can be deactivated by any unauthenticated user. It is possible to retrieve a reset token which can then be used to deactivate the plugin. CVE record
What to do if you run Hide My WP Ghost
If you run Hide My WP Ghost, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Hide My WP Ghost vulnerabilities
Free. We email you when a new vulnerability is published for Hide My WP Ghost, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.