WP Timetics- AI-powered Appointment Booking Calendar and Online Scheduling Plugin <= 1.0.25 - Insecure Direct Object Reference to Unauthenticated Arbitrary User Password/Email Reset/Account Takeover
Strategic Overview
- Status
- Patched in 1.0.26
- Affected Plugin
- Timetics – Appointment Booking Calendar & Scheduling
- Affected Version
<= 1.0.25- CVSS
- 9.8Critical
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-9263
At a glance
CVE-2024-9263 is a critical-severity Authorization Bypass Through User-Controlled Key vulnerability in the Timetics WordPress plugin, affecting versions <= 1.0.25. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.26; sites on affected versions should update now. Disclosed October 2024, reported by wesley (wcraft).
Vulnerability Overview
The WP Timetics- AI-powered Appointment Booking Calendar and Online Scheduling Plugin plugin for WordPress is vulnerable to Account Takeover/Privilege Escalation via Insecure Direct Object Reference in all versions up to, and including, 1.0.25 via the save() due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to reset the emails and passwords of arbitrary user accounts, including administrators, which makes account takeover and privilege escalation possible.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-639: Authorization Bypass Through User-Controlled Key
Timetics <= 1.0.25 carries this weakness at save(), and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Timetics the fix is 1.0.26: builds <= 1.0.25 are affected, anything from 1.0.26 onward is not.
Remediation
Update to version 1.0.26, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Timetics 1.0.26 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Timetics – Appointment Booking Calendar & Scheduling
- 7.3CVE-2024-1094: Timetics- AI-powered… Limited Privilege Escalation
CVE-2024-1094 - 7.2CVE-2026-57674: Timetics Stored XSS
CVE-2026-57674 - 6.5CVE-2025-5919: Appointment Booking… Unauthenticated Booking Details
CVE-2025-5919 - 5.3CVE-2026-84215: Timetics Missing Authorization
CVE-2026-84215 - 5.3CVE-2026-14322: Timetics <= 1.0.56 Unauthenticated Booking Approval
CVE-2026-14322 - 5.3CVE-2026-39432: Timetics Missing Authorization
CVE-2026-39432 - 5.3CVE-2025-15473: Timetics Missing Authorization
CVE-2025-15473 - 5.3CVE-2025-67915: Timetics Incorrect Authorization
CVE-2025-67915
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C