Appointment Bookings for Zoom GoogleMeet and more – Wappointment <= 2.7.6 - Unauthenticated Insecure Direct Object Reference via Predictable 'edit_key' / 'appointmentkey' Parameter
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.
Quick answer
Appointment Bookings for Zoom GoogleMeet and more – Wappointment should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-2.7.6
Fixed versions
- 2.7.7
How to fix it
Wappointment is affected by CVE-2026-9188, unauthenticated insecure direct object reference through predictable edit_key or appointmentkey values in *-2.7.6. Prioritize production WordPress sites where the plugin or theme is enabled, especially if unauthenticated users can reach the vulnerable workflow. The recommended remediation is to update to version 2.7.7 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable feature, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses Wappointment, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with the affected range: *-2.7.6.
- Apply the remediation: update to version 2.7.7 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable Wappointment or restrict the affected admin, REST, AJAX, shortcode, upload, booking, ecommerce, profile, form, gallery, or theme workflow to trusted administrators only.
- Review application, web server, WordPress security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-9188.
- Remove suspicious stored content, uploaded files, generated logs, injected scripts, unexpected appointments/orders/posts, or altered configuration created through the affected workflow.
- Clear application, object, page, CDN, and browser caches after remediation so stale vulnerable responses or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Wappointment is no longer running *-2.7.6 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated users can no longer trigger the affected action or access data outside their intended permissions.
- Review logs before and after the fix for exploitation attempts, suspicious role activity, unexpected content changes, file reads, SQL errors, or unauthorized data access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-9188?
Appointment Bookings for Zoom GoogleMeet and more – Wappointment versions listed as affected should be reviewed: *-2.7.6.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.