CVE-2026-86841

Bookly 23.2 - 28.2 - Authenticated (Bookly Administrator+) PHP Object Injection

Strategic Overview

Status
Patched in 28.3
Affected Version
23.2 – 28.2
CVSS
7.5High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2026-86841
View all Online Scheduling and Appointment Booking System – Bookly vulnerabilities

At a glance

CVE-2026-86841 is a high-severity Deserialization of Untrusted Data vulnerability in the Online Scheduling and Appointment Booking System WordPress plugin, affecting versions 23.2 – 28.2. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Bookly Administrator level or above. The issue is fixed in version 28.3; sites on affected versions should update now. Disclosed September 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The Bookly plugin for WordPress is vulnerable to PHP Object Injection in versions 23.2 through 28.2. This is due to deserialization of untrusted input. This makes it possible for authenticated attackers, with bookly administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Reaching this weakness in Online Scheduling and Appointment Booking System 23.2 – 28.2 takes an account at Bookly Administrator level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Online Scheduling and Appointment Booking System the fix is 28.3: builds 23.2 – 28.2 are affected, anything from 28.3 onward is not.

Remediation

Update to version 28.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Bookly Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Online Scheduling and Appointment Booking System 28.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C