Skip to content
Noroxi

Rox Appointment Booking – Event, Calendar & Appointment Scheduling

rox-appointment-booking · plugin

Known security vulnerabilities for Rox Appointment Booking – Event, Calendar & Appointment Scheduling. Find out in seconds which version runs on your site with WP Lens.

6 known vulnerabilities

6 exploitable without logging in · latest Oct 31, 2026

Before you install

Use with care

  • 6 records needing no login published in the last two years.

If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.

This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.

Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector

Listed on wordpress.org · latest 1.3.3 · last updated Nov 2, 2026 · 2K+ installs

wordpress.org status checked on Nov 5, 2026

Vulnerabilities

  • CVE-2026-104012unauthenticated · needs a click≤ 1.3.1

    Rox Appointment Booking <= 1.3.1 - Unauthenticated Privilege Escalation via Mass Assignment to Mass Assignment via '/public/booking' Endpoint

    High 8.8
  • CVE-2026-87891unauthenticated→ 1.2.0

    Rox Appointment Booking < 1.2.0 - Unauthenticated Holiday Schedule Modification via REST API

    Medium 6.5
  • CVE-2026-87907unauthenticated→ 1.2.8

    Rox Appointment Booking < 1.2.8 - Unauthenticated Internal Notes Disclosure via Service and Category REST Routes

    Medium 5.3
  • CVE-2026-87896unauthenticated→ 1.2.8

    Rox Appointment Booking < 1.2.8 - Unauthenticated Staff PII Disclosure via Agent REST Route

    Medium 5.3
  • CVE-2026-87894unauthenticated→ 1.2.3

    Rox Appointment Booking 1.0.9 - 1.2.2 - Unauthenticated Customer PII Disclosure via IDOR

    Medium 5.3
  • CVE-2026-87892unauthenticated→ 1.2.0

    Rox Appointment Booking < 1.2.0 - Unauthenticated Price Manipulation and Payment Method Restriction Bypass

    Medium 5.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory