HomeWordPress vulnerabilitiesAppointment Bookings for Zoom GoogleMeet and more
Appointment Bookings for Zoom GoogleMeet and more vulnerabilities
Appointment Bookings for Zoom GoogleMeet and more has 2 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 1,000+
- Latest version
- 2.7.7
- Last updated
- 24 May 2026
- Most recent
- 6 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-39756 | Medium 6.5 | Up to 2.7.7 | No fixed version yet | 1 d ago |
| Broken access control CVE-2026-9188 | Medium 5.3 | Up to 2.7.6 | Fixed in a later version (latest 2.7.7) | 2 Jul 2026 |
Read the published descriptions
- CVE-2026-39756, 6 Oct 2026
- Unauthenticated Insecure Direct Object References (IDOR) in Wappointment <= 2.7.7 versions. CVE record
- CVE-2026-9188, 2 Jul 2026
- The Appointment Bookings for Zoom GoogleMeet and more - Wappointment plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to and including 2.7.6 via the `appointmentkey` parameter due to the appointment `edit_key` - the sole authorization token consumed by `tryCancel()` - being generated as a predictable, unsalted MD5 hash of only `client_id` (a sequential integer), `start_at` (a publicly observable appointment timestamp), and `staff_id` (a small enumerable integer), with no secret salt or random component, and the unauthenticated cancellation and rescheduling REST endpoints performing no ownership or identity verification beyond matching this reconstructible key. This makes it possible for unauthenticated attackers to compute valid `edit_key` values for appointments belonging to other users and cancel or reschedule those appointments arbitrarily. Exploitation requires the `allow_cancellation` or `allow_rescheduling` setting to be enabled on the site, both of which are common configurations for active booking deployments; an attacker can obtain the inputs needed to reconstruct a victim's key by booking their own appointment to observe their sequential `client_id` and correlating publicly visible appointment times and enumerable staff identifiers. CVE record
What to do if you run Appointment Bookings for Zoom GoogleMeet and more
If you run Appointment Bookings for Zoom GoogleMeet and more, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Appointment Bookings for Zoom GoogleMeet and more vulnerabilities
Free. We email you when a new vulnerability is published for Appointment Bookings for Zoom GoogleMeet and more, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.