Subscriber Broken Authentication in Hide My WP Ghost <= 7.0.06 versions.
CVE-2026-59546
Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
July 27, 2026
Last Modified
July 27, 2026
Advisory Details (1)
Auto-updated Jul 27, 2026Broken Authentication in WordPress Hide My WP Ghost Plugin - Patchstack
https://patchstack.com/database/wordpress/plugin/hide-my-wp/vulnerability/wordpress-hide-my-wp-ghost-plugin-7-0-06-2fa-bypass-vulnerability?_s_id=cveVendor Advisories for CVE-2026-59546(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 07:14 UTCGHSA enrichment
- 2026-07-28 18:46 UTCEG score recompute
- 2026-07-28 18:46 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 06:17 UTCGHSA enrichment
- 2026-07-27 17:49 UTCGHSA enrichment
- 2026-07-27 16:25 UTCEG score recompute
- 2026-07-27 16:25 UTCGHSA enrichment
- 2026-07-27 16:17 UTCEG score recompute
- 2026-07-27 16:17 UTCGHSA enrichment
- 2026-07-27 15:22 UTCEG score recompute
- 2026-07-27 14:26 UTCEG score recompute
- 2026-07-27 14:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-59546?
When was CVE-2026-59546 disclosed?
Is CVE-2026-59546 actively exploited?
What is the CVSS score of CVE-2026-59546?
How do I remediate CVE-2026-59546?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59546
Is Your Infrastructure Affected by CVE-2026-59546?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.