# 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.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-796c-rm6v-rccx

## 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 (Authorization Bypass Through User-Controlled Key)

## 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.

## Is CVE-2026-9180 being exploited?

There is no known exploitation of CVE-2026-9180 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9180 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-9180 in the wild and no public exploit code.

Affected product: jetmonsters MotoPress Appointment Booking. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9180/ (Markdown: https://insights.sbomify.com/CVE-2026-9180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9180
- OSV: https://osv.dev/vulnerability/CVE-2026-9180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9180/
Summaries are generated and may contain mistakes; the official description above is the record.