dbcve.org
Hide My Wp GhostWordPress extension · Wpplugins

CVE-2023-34001

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 5.0.26 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Restriction of Excessive Authentication Attempts vulnerability in WPPlugins – WordPress Security Plugins Hide My WP Ghost allows Functionality Bypass.This issue affects Hide My WP Ghost: from n/a through 5.0.25.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Hide My WP Ghost WordPress security plugin versions up to 5.0.25 contain an Improper Restriction of Excessive Authentication Attempts vulnerability that allows bypassing rate limiting on authentication. This enables attackers to conduct unlimited login attempts without triggering lockout protections, facilitating brute force attacks against WordPress admin accounts.

MitigationUpdate Hide My WP Ghost to the latest version (5.0.26 or later) which contains the fix for this authentication bypass. Additionally, implement supplementary brute force protections such as two-factor authentication, IP-based rate limiting at the server level, or complementary security plugins until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hide My Wp GhostWordPress extension
Affected:< 5.0.26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Hide My WP Ghost is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/hide-my-wp-ghost directory on the server
    Affected if The plugin is present on the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Hide My WP Ghost to view the version number, or read the main plugin file (such as hide-my-wp.php) which contains a version constant
    Affected if The installed version is below 5.0.26 (versions 5.0.25 and earlier)
  3. Confirm rate limiting protection is enabled
    In WordPress admin, go to Hide My WP Ghost settings and check if the Brute Force Protection or Login Protection feature is turned on
    Affected if The rate limiting or brute force protection module is active in the plugin settings
  4. Inspect authentication attempt logs
    Review Hide My WP Ghost security logs or server access logs for any patterns of rapid repeated login attempts that did not trigger lockout or rate limiting blocks
    Affected if Multiple failed login attempts from a single source are not being blocked or rate-limited as expected

You are affected if the Hide My WP Ghost plugin is installed with a version below 5.0.26 and the brute force or login protection feature is enabled, allowing unlimited authentication attempts without triggering lockout protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.26 or later
Fixed in 5.0.26
Interim mitigation

Update Hide My WP Ghost to the latest version (5.0.26 or later) which contains the fix for this authentication bypass. Additionally, implement supplementary brute force protections such as two-factor authentication, IP-based rate limiting at the server level, or complementary security plugins until the update is applied.

Recommended fix Moderate confidence

Hide My WP Ghost version 5.0.26

  1. 1. Create a full backup of your WordPress site including database and files
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find 'Hide My WP Ghost' plugin in the installed plugins list
  4. 4. Click 'Update Now' if an update is available, or manually upload version 5.0.26
  5. 5. After updating, verify the plugin is running version 5.0.26 in the Plugins list
  6. 6. Test that the Hide My WP Ghost functionality works correctly (e.g., login protection, firewall rules)
  7. 7. Test front-end and back-end functionality to ensure no conflicts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hide My Wp Ghost Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34001 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data