CVE-2026-86839: Online Scheduling and Appointment Booking System (WordPress plugin) · Insecure Direct Object Reference
Affects Online Scheduling and Appointment Booking System (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 3.8 Low : upgrade to 28.3 when convenient.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 28.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 11 Nov 2026.
What to do
Upgrade Online Scheduling and Appointment Booking System (WordPress plugin) to 28.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Online Scheduling and Appointment Booking System | Affected
| Fixed in
|
AI-suggested
Upgrade the Online Scheduling and Appointment Booking System WordPress plugin to version 28.3 or later, where this authorization bypass vulnerability is fixed. No other mitigation steps are indicated. Patch status is confirmed by the version boundary provided.
Description
The Online Scheduling and Appointment Booking System WordPress plugin before version 28.3 contains an authorization bypass vulnerability. Authenticated users with staff-level privileges can access, modify, or delete appointment and payment records of other staff members without proper verification. This includes access to associated customer personal information. The vulnerability arises because the plugin does not verify that the requested records belong to the requesting staff member in its staff-role AJAX actions.