Skip to main content
VulnerabilityPublished

CVE-2026-87894: Rox Appointment Booking (WordPress plugin) · Insecure Direct Object Reference

Affects Rox Appointment Booking (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.2.3 when convenient.

Data as of 28 Oct 2026, 05:12 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Rox Appointment Booking (WordPress plugin) to 1.2.3.

Affected software

ProductAffectedFixed in
Rox Appointment BookingAffected
  • >=1.0.9 <1.2.3
Fixed in
  • 1.2.3

AI-suggested

Upgrade the Rox Appointment Booking plugin to version 1.2.3 or later, where authorization checks on the booking confirmation endpoint have been implemented. If you cannot patch yet, restrict access to the endpoint if possible or disable the plugin to prevent unauthorized data disclosure.

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.

References

Community reviews

Loading reviews…