CVE-2026-126039 json
WP Ghost (Hide My WP Ghost) < 7.0.19 - Unauthenticated Stored XSS via Comment Author Name
published 22h ago modified 22h ago also EUVD-2026-132003
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
The Hide My WP Ghost WordPress plugin before 7.0.19 does not limit one of its HTML output rewriting patterns to the markup it targets, allowing unauthenticated attackers to inject HTML attributes through a comment author name that execute as Stored XSS for any visitor, including logged-in administrators, on pages that list recent comments.
Patch / fix
- Unknown Hide My WP Ghost 7.0.19
Is CVE-2026-126039 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-21).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/9b70c614-11ee-4ca0-b204-8127fcd1ffa5/ referenced PoC, tagged "exploit" by a source, unverified
Affected products
- Unknown Hide My WP Ghost
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/9b70c614-11ee-4ca0-b204-8127fcd1ffa5/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-126039
- NVD CVE-2026-126039
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.