CVE-2025-67915

Timetics <= 1.0.46 - Incorrect Authorization to Authenticated (Timetics Customer+) User Creation

2026-01-05 00:00
daroo

Strategic Overview

Status
Patched in 1.0.48
Affected Version
<= 1.0.46
CVSS
5.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2025-67915
View all Timetics – Appointment Booking Calendar & Scheduling vulnerabilities

At a glance

CVE-2025-67915 is a medium-severity Incorrect Authorization vulnerability in the Timetics WordPress plugin, affecting versions <= 1.0.46. 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.48; sites on affected versions should update now. Disclosed January 2026, reported by daroo.

Vulnerability Overview

The Appointment Booking Calendar – WP Timetics Booking Plugin plugin for WordPress is vulnerable to unauthorized access due to a insufficient capability check in the api-customer.php file in all versions up to, and including, 1.0.46. This makes it possible for authenticated attackers, with Timetics Customer-level access and above, to create arbitrary user accounts.

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-863: Incorrect Authorization

Reaching this weakness in Timetics <= 1.0.46 takes an account at Timetics Customer level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Timetics the fix is 1.0.48: builds <= 1.0.46 are affected, anything from 1.0.48 onward is not.

Remediation

Update to version 1.0.48, 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: Timetics 1.0.48 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