CVE-2026-87894

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

Published Sep 12, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Rox Appointment Booking plugin for WordPress versions 1.0.9 through 1.2.2 contains a missing authorization check on the booking confirmation endpoint. Each booking is addressed by a sequential numeric identifier, which allows an attacker with no authentication to request any booking ID and receive the customer’s name, email, phone number, booking details and payment status. This secure Direct Object References vulnerability and results in sensitive customer data being disclosed to unauthenticated users.

Affected Systems

WordPress sites that have the Rox Appointment Booking plugin installed in any version from 1.0.9 up to but not including 1.2.3.

Risk and Exploitability

The flaw relies solely on the absence of access‑control logic; an attacker only needs to guess or systematically iterate through booking identifiers to expose data. The likely attack vectorSS score of 5.3 indicates moderate severity, while the EPSS score of less than 1% indicates a low probability of exploitation in the wild. The vulnerability is not listed in CISA KEV, suggesting no known large‑scale exploitation. Nonetheless, the exposure of customer PII can have serious confidentiality implications if accessed by a determined attacker.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Rox Appointment Booking plugin to version 1.2.3 or newer, which implements the missing authorization check on the booking confirmation endpoint.
  • If an update is not immediately possible, to require authentication (for example, enforce login or apply IP restrictions) before allowing access to the booking detail URLs.
  • Review the plugin’s source code or documentation to confirm that no additional access‑control gaps remain.

Generated by OpenCVE AI on September 15, 2026 at 18:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions rox Appointment Booking
Vendors & Products Wordpress-extensions
Wordpress-extensions rox Appointment Booking
Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-284
CWE-639
Type Values Removed Values Added
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.
Title Rox Appointment Booking 1.0.9 - 1.2.2 - Unauthenticated Customer PII Disclosure via IDOR
References
Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Sep 12, 2026, 3:28 PM
Reserved
Sep 9, 2026, 2:58 PM
Status
Deferred
Published
Sep 12, 2026, 6:16 AM
Modified
Sep 14, 2026, 9:10 PM