Rox Appointment Booking exposes sequential customer records
Rox Appointment Booking from 1.0.9 through versions before 1.2.3 returns booking confirmation details without authorization and addresses each booking with a sequential numeric identifier. An unauthenticated attacker can enumerate IDs to obtain customer names, email addresses, phone numbers, booking details, and payment status. The authoritative export does not name the endpoint or identifier parameter.
- Component
- Rox Appointment Booking
- Plugin slug
rox-appointment-booking- Affected
- 1.0.9 to < 1.2.3
- Safe version
1.2.3- Published
- Sep 12, 2026
This CVE was published Sep 12, 2026 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update Rox Appointment Booking to 1.2.3 or later. The authoritative affected range ends before 1.2.3. The application-level fix must authorize access to the specific booking and use unguessable confirmation tokens as defense in depth rather than trusting a sequential ID.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Rox Appointment Booking WordPress plugin before 1.2.3 does not perform any authorization check on the endpoint that returns a booking's confirmation details, and each booking is addressed by a sequential numeric identifier, allowing unauthenticated attackers to read any customer's name, email, phone, booking details and payment status by enumerating that identifier.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N