Get Bookings WpWordPress extension · Istmoplugins
CVE-2024-13677
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 · uneditedThe GetBookingsWP – Appointments Booking Calendar Plugin For WordPress plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.1.27. This is due to the plugin not properly validating a user's identity prior to updating their details like email. This makes it possible for authenticated attackers, with subscriber-level access and above, to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.
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 confidenceThe GetBookingsWP WordPress plugin fails to validate user identity before allowing updates to user details such as email addresses. This allows any authenticated user with subscriber-level access or higher to change the email address of arbitrary users, including administrators, and then abuse the password reset function to take over those accounts.
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
Get Bookings WpWordPress extension
<= 1.1.27CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, locate 'Get Bookings WP' by Istmoplugins, and read the version number displayed. Alternatively, check the plugin header in wp-content/plugins/get-bookings-wp/get-bookings-wp.php for the Version: x.x.x field.Affected if The version is 1.1.27 or lower (any version up to and including 1.1.27). Versions 1.1.28 and later are patched.
-
Verify plugin is activeConfirm the Get Bookings WP plugin is currently activated on the WordPress site. Check the Plugins screen for a 'Active' status indicator next to the plugin.Affected if The plugin is active and vulnerable versions (1.1.27 or lower) are running.
-
Review user profiles for unauthorized email changesIn WordPress admin, go to Users > All Users. For each user (especially administrators), click to edit the profile and compare the current email address against any known legitimate values, records of previous emails, or external documentation of expected accounts.Affected if Any user account shows an email address that was changed without authorization or that does not match the original registered email.
-
Check for suspicious password reset requestsReview WordPress server logs, access logs, or the wp_options table for recent password reset key generations. Look for password reset emails sent to users who did not request them, or check the wp_login_log or similar audit logs if available.Affected if Password reset emails were triggered for accounts whose emails were recently changed, indicating potential exploitation.
-
Inspect plugin endpoints for IDOR indicatorsIf access to the site's AJAX or REST endpoints is available, examine network traffic or server logs for requests to the plugin's profile update functionality (typically wp-admin/admin-ajax.php action=gbw_update_profile or similar) where the user_id parameter can be manipulated to modify other users' profiles.Affected if Multiple or repeated profile update requests exist targeting different user IDs from low-privilege accounts (subscriber level).
You are affected if Get Bookings WP version 1.1.27 or lower is active on your WordPress site, regardless of whether you have already observed unauthorized email changes.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the plugin to version 1.1.28 or later which implements proper identity validation. Additionally, audit user accounts for unauthorized email changes and reset passwords for any compromised administrator accounts.
Update to GetBookingsWP version 1.1.28 or latest available version
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'GetBookingsWP – Appointments Booking Calendar Plugin For WordPress'
- If an update is available, click 'Update Now' to update to the latest version
- After updating, verify the version number is 1.1.28 or higher
- Review existing user accounts in Users > All Users for any unauthorized changes
- As a precaution, consider resetting passwords for administrator-level accounts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Get Bookings Wp
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13677 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13677 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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