CVE-2026-7527

WP Ghost (Hide My WP Ghost) <= 7.0.02 - Unauthenticated Open Redirect via 'redirect_to' Parameter

2026-09-18 19:00
s00me00ne

Strategic Overview

Status
Patched in 7.0.03
Affected Plugin
Hide My WP Ghost – Security & Firewall
Affected Version
<= 7.0.02
CVSS
4.7Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2026-7527
View all Hide My WP Ghost – Security & Firewall vulnerabilities

At a glance

CVE-2026-7527 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Hide My WP Ghost WordPress plugin, affecting versions <= 7.0.02. It carries a CVSS score of 4.7 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.0.03; sites on affected versions should update now. Disclosed September 2026, reported by s00me00ne.

Vulnerability Overview

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.

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.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Hide My WP Ghost <= 7.0.02 carries this weakness at wp_logout(), and reaching it takes no account at all. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For Hide My WP Ghost the fix is 7.0.03: builds <= 7.0.02 are affected, anything from 7.0.03 onward is not.

Remediation

Update to version 7.0.03, or a newer patched version

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. None of that substitutes for the fix: Hide My WP Ghost 7.0.03 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-7527https://www.wordfence.com/threat-intel/vulnerabilities/id/bd88ebd2-5584-4886-9c85-39a225cd00e9https://nvd.nist.gov/vuln/detail/CVE-2026-7527

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C