CVE-2026-9180 Missing authorization in MotoPress Appointment Booking
Unauthenticated attackers can modify customer details of pending bookings by exploiting an insecure direct object reference in the MotoPress Appointment Booking plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-9180?
CVE-2026-9180 is a medium-severity missing authorization vulnerability in jetmonsters MotoPress Appointment Booking, published on 3 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The MotoPress Appointment Booking plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to, and including, 2.4.4. This is due to the `POST /motopress/appointment/v1/bookings` REST endpoint being registered with `'permission_callback' => '__return_true'`, allowing unauthenticated access, while the `createBooking` handler in `BookingsRestController.php` accepts an attacker-supplied `payment_details.booking_id` value and loads the referenced booking via `findById()` without verifying that the caller owns or has any rights to that booking. This makes it possible for unauthenticated attackers to overwrite the customer name, email address, phone number, and `customer_id` of any non-confirmed victim booking by submitting a request with no reservation items, causing `BookingService::createBooking()` to load the existing victim booking object and persist it with attacker-controlled customer data. Victim booking IDs can be harvested prior to exploitation without authentication by querying the also-publicly-accessible `GET /motopress/appointment/v1/bookings/reservations` endpoint with a guessable `service_id` and date range, and only bookings whose status is not `STATUS_CONFIRMED` (e.g., pending or auto-draft) are valid targets.
Weakness: CWE-639
Which versions are affected by CVE-2026-9180?
How do I fix CVE-2026-9180?
No fix has been published for CVE-2026-9180 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-9180 being exploited?
There is no known exploitation of CVE-2026-9180 in the wild and no public exploit code.
Sources
Also known as GHSA-796c-rm6v-rccx.