The Hide My WP Ghost WordPress plugin before 7.0.19 does not limit one of its HTML output rewriting patterns to the
Source GCVE Database
Not known to be exploited : upgrade to 7.0.19 soon.
Data as of 21 Nov 2026, 07:16 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 7.0.19
Exploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Hide My WP Ghost to 7.0.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Hide My WP Ghost | Affected
| Fixed in
|
AI-suggested
A fix is available in Hide My WP Ghost version 7.0.19. Users should update to version 7.0.19 or later to remediate this vulnerability. No other mitigation steps are indicated by the available data.
Description
The Hide My WP Ghost WordPress plugin versions prior to 7.0.19 contain a vulnerability where an HTML output rewriting pattern is not properly limited to its intended markup. This flaw allows unauthenticated attackers to inject HTML attributes via the comment author name, resulting in stored cross-site scripting (XSS) that executes for any visitor, including logged-in administrators, on pages displaying recent comments.