Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-9180 medium CVSS 5.3

Vulnerability in MotoPress Appointment Booking (WordPress plugin) (CVE-2026-9180)

Summary

Vulnerability in MotoPress Appointment Booking (WordPress plugin) (CVE-2026-9180). Risk of unauthorized operations or information disclosure. Exploitable via POST /motopress/appointment/v1/bookings.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-9180 has been found in MotoPress Appointment Booking (WordPress plugin).
Attackers can target a specific entry point like POST /motopress/appointment/v1/bookings over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "MotoPress Appointment Booking (WordPress plugin) CVE-2026-9180" on the vendor's site.

CVE-2026-9180 (MotoPress Appointment Booking (WordPress plugin)) — CWE-639 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /motopress/appointment/v1/bookings / GET /motopress/appointment/v1/bookings/reservations / createBooking / BookingsRestController.php
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in MotoPress Appointment Booking (WordPress plugin). Attackers reach the vulnerable code path via POST /motopress/appointment/v1/bookings without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of MotoPress Appointment Booking (WordPress plugin). Attack surface: POST /motopress/appointment/v1/bookings / GET /motopress/appointment/v1/bookings/reservations / createBooking / BookingsRestController.php.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /motopress/appointment/v1/bookings requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで MotoPress Appointment Booking (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /motopress/appointment/v1/bookings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /motopress/appointment/v1/bookings への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /motopress/appointment/v1/bookings on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details