CVE-2026-86838: Bookly WordPress plugin payment bypass via booking price manipulation

CVE-2026-86838 · Severity: medium · CVSS 5.3 · Published 2026-09-28

Bookly is a WordPress plugin for managing appointment bookings and payments. The plugin fails to validate booking quantity values on the server, allowing attackers to manipulate prices and book paid services for free by bypassing payment requirements entirely.

Technologies: Bookly. Vendors: Bookly.

Quick answers

Is CVE-2026-86838 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-86838 being exploited in the wild.
How severe is CVE-2026-86838?
Medium severity, with a CVSS score of 5.3, published 28 September 2026.
Which products and versions are affected?
Bookly before 28.3.
Is there a fix for CVE-2026-86838?
A patch was published on 2026-09-28: Version 28.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-86838 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-86838?
Check whether you run Bookly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a business logic flaw where client-supplied booking quantity values are not validated server-side before computing appointment totals. An unauthenticated attacker can manipulate the quantity parameter to reduce the total price to zero, bypassing the payment processing step and completing bookings at no cost.

Affected products

  • Bookly Bookly before 28.3

Timeline

  • 2026-09-25: disclosed
  • 2026-09-28: patched: Version 28.3 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.