Appointment Bookings For Zoom Googlemeet And More – Wappointment
Approved changes feed: RSS · Atom
cpe:2.3:a:wappointment:appointment_bookings_for_zoom_googlemeet_and_more_–_wappointment:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Wappointment (1d22ad8c-e6c4-5d87-9b0d-d01a17d55d36) |
|---|---|
| Product | Appointment Bookings For Zoom Googlemeet And More – Wappointment (1c3248c8-e2f0-51fa-95a2-bdd64e0736b8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-9188 |
vulnerable | 2026-07-29 01:09:06.780096 |
Appointment Bookings for Zoom GoogleMeet and more – Wappointment <= 2.7.6 - Unauthenticated Insecure Direct Object Reference via Predictable 'edit_key' / 'appointmentkey' Parameter
MEDIUM (5.3)
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.
Published: 2026-07-02T08:33:04.439Z
Updated: 2026-07-02T19:41:53.548Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32454 |
vulnerable | 2026-06-08 06:35:33.147796 |
WordPress Wappointment plugin <= 2.6.0 - Server Side Request Forgery (SSRF) vulnerability
MEDIUM (4.4)
Server-Side Request Forgery (SSRF) vulnerability in Wappointment Appointment Bookings for Zoom GoogleMeet and more – Wappointment.This issue affects Appointment Bookings for Zoom GoogleMeet and more – Wappointment: from n/a through 2.6.0.
Published: 2024-04-15T07:13:07.050Z
Updated: 2026-04-28T16:09:35.915Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.