Hide My Wp Ghost Security Firewall
Monthly
Stored cross-site scripting in the WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress versions up to and including 7.0.12 lets unauthenticated attackers inject arbitrary web scripts through the plugin's replaceHeadersAndTags function, which performs insufficient input sanitization and output escaping; the injected payload persists and executes in a victim's browser when they click the crafted link, with impact limited to that victim's session (no availability impact). Exploitation requires the affected code path to be reachable on a site running 7.0.12 or earlier, but no authentication (CVSS PR:N) and no special non-default plugin configuration; although the published CVSS 3.1 vector scores UI:N, the practical trigger is a victim clicking the injected link, which is why our assessment adjusts user interaction to UI:R while keeping the same 7.2 base impact. The vendor has released a fix in version 7.0.13 (WordPress.org changeset from 7.0.12 to 7.0.13), no public exploit code has been identified and there is no CISA KEV entry indicating active exploitation at time of analysis. Reported by Wordfence, a credible source for WordPress plugin vulnerability intelligence.
Open redirect in the WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress, affecting all versions up to and including 7.0.02, allows an unauthenticated attacker to bounce a victim to an arbitrary external site by crafting a logout link whose destination the plugin never validates. Exploitation is not hands-off: the attacker must socially engineer a currently logged-in user into clicking the crafted URL, and because the plugin's logout routine invokes wp_logout() before issuing the redirect, the victim is fully and irreversibly logged out as part of the attack chain, though the practical harm remains limited to redirection to a malicious page. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the 4.7 vendor score is consistent with the UI:R social-engineering gate combined with a scope change and low integrity impact.
Stored cross-site scripting in the WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress versions up to and including 7.0.12 lets unauthenticated attackers inject arbitrary web scripts through the plugin's replaceHeadersAndTags function, which performs insufficient input sanitization and output escaping; the injected payload persists and executes in a victim's browser when they click the crafted link, with impact limited to that victim's session (no availability impact). Exploitation requires the affected code path to be reachable on a site running 7.0.12 or earlier, but no authentication (CVSS PR:N) and no special non-default plugin configuration; although the published CVSS 3.1 vector scores UI:N, the practical trigger is a victim clicking the injected link, which is why our assessment adjusts user interaction to UI:R while keeping the same 7.2 base impact. The vendor has released a fix in version 7.0.13 (WordPress.org changeset from 7.0.12 to 7.0.13), no public exploit code has been identified and there is no CISA KEV entry indicating active exploitation at time of analysis. Reported by Wordfence, a credible source for WordPress plugin vulnerability intelligence.
Open redirect in the WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress, affecting all versions up to and including 7.0.02, allows an unauthenticated attacker to bounce a victim to an arbitrary external site by crafting a logout link whose destination the plugin never validates. Exploitation is not hands-off: the attacker must socially engineer a currently logged-in user into clicking the crafted URL, and because the plugin's logout routine invokes wp_logout() before issuing the redirect, the victim is fully and irreversibly logged out as part of the attack chain, though the practical harm remains limited to redirection to a malicious page. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the 4.7 vendor score is consistent with the UI:R social-engineering gate combined with a scope change and low integrity impact.