dbcve.org
WpbookitWordPress extension · Iqonic

CVE-2024-10215

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 1.6.6 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The WPBookit plugin for WordPress is vulnerable to Arbitrary User Password Change in versions up to, and including, 1.6.4. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for unauthenticated attackers to change user passwords and potentially take over administrator accounts.

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 · high confidence

The WPBookit WordPress plugin up to version 1.6.4 contains an IDOR (Insecure Direct Object Reference) vulnerability allowing unauthenticated attackers to change arbitrary user passwords by manipulating user IDs in password reset requests. The plugin fails to validate authorization before allowing password modifications, enabling complete administrator account takeover.

MitigationUpdate WPBookit plugin to version 1.6.5 or later. If no update is available, deactivate the plugin immediately and consider removing it entirely. Review user accounts for unauthorized changes.

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
WpbookitWordPress extension
Affected:< 1.6.6

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
High
Integrity
High
Availability
High

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

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. Locate WPBookit plugin installation
    Check your WordPress installation for the WPBookit plugin directory in wp-content/plugins/ or view it in the WordPress admin under Plugins > Installed Plugins
    Affected if The WPBookit plugin is present in your WordPress installation
  2. Identify installed version
    View the plugin details in WordPress admin (Plugins page) or check the main plugin file (usually wpbookit.php) for the version comment/header
    Affected if The displayed version number is lower than 1.6.6 (for example, 1.6.4 or earlier)
  3. Verify password reset functionality exists
    Check if the plugin includes user account management features, particularly password reset or user profile update functionality by examining plugin files for functions handling password changes or user ID parameters
    Affected if The plugin contains password reset or user profile update endpoints that accept user ID parameters without proper authorization checks
  4. Test unauthorized password change (optional/careful)
    If you have a test environment, examine if the plugin's password reset endpoint can be accessed without authentication and allows manipulation of user IDs to change arbitrary user passwords
    Affected if The password reset mechanism accepts unauthenticated requests and does not validate authorization before changing passwords for arbitrary user IDs

Your environment is affected if the WPBookit plugin is installed with a version lower than 1.6.6 and includes user password change functionality accessible without authentication.

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 1.6.6 or later
Fixed in 1.6.6
Interim mitigation

Update WPBookit plugin to version 1.6.5 or later. If no update is available, deactivate the plugin immediately and consider removing it entirely. Review user accounts for unauthorized changes.

Recommended fix High confidence

1.6.6

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WPBookit in the plugin list
  4. Check if current version is below 1.6.6
  5. Click 'Update Now' on the WPBookit plugin card if an update is available
  6. Alternatively, navigate to Dashboard > Updates and update WPBookit from there
  7. After updating, verify the new version is 1.6.6 or higher in the plugins list
  8. Test that the booking functionality still works correctly
Caveat Review plugin settings and test booking workflows after upgrade to ensure compatibility with your setup

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

Fix this in Wpbookit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10215 — 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-2024-10215 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