CVE-2026-11446

Booktics – Booking Calendar for Appointments and Service Businesses <= 1.0.23 - Missing Authorization

2026-09-10 14:53
revblock

Strategic Overview

Status
Patched in 1.0.24
Affected Version
<= 1.0.23
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-11446
View all Booktics – Appointment Booking Calendar for Service Businesses vulnerabilities

At a glance

CVE-2026-11446 is a medium-severity Missing Authorization vulnerability in the Booktics WordPress plugin, affecting versions <= 1.0.23. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.24; sites on affected versions should update now. Disclosed September 2026, reported by revblock.

Vulnerability Overview

The Booktics – Booking Calendar for Appointments and Service Businesses plugin for WordPress is vulnerable to unauthorized modification of data in all versions up to, and including, 1.0.23. This is due to the create_order_permission() permission callback on the POST /wp-json/booktics/v1/orders REST route unconditionally returning true, combined with find_and_update_guest() overwriting an existing customer record's stored name, phone, and wp_user_id whenever the caller-supplied email matches, with no proof of ownership. This makes it possible for unauthenticated attackers to overwrite the contact details (name and phone) of any existing customer whose email address they know, poisoning downstream reminder emails, SMS, calendar invites, and CRM data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Booktics <= 1.0.23 carries this weakness at create_order_permission(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Booktics the fix is 1.0.24: builds <= 1.0.23 are affected, anything from 1.0.24 onward is not.

Remediation

Update to version 1.0.24, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Booktics 1.0.24 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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