Quick answers
- Is CVE-2026-14322 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14322 being exploited in the wild.
- How severe is CVE-2026-14322?
- Informational severity, with a CVSS score of 5.3, published 22 July 2026.
- Which products and versions are affected?
- Timetics Timetics before 1.0.57.
- Is there a fix for CVE-2026-14322?
- A patch was published on 2026-07-22: Fixed in version 1.0.57 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14322 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-14322?
- Check whether anything you run is named in the advisory. 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
An improper access control vulnerability exists in the Timetics WordPress plugin's REST API endpoint (/wp-json/timetics/v1/bookings). The plugin does not validate or enforce a 'pending' or 'unpaid' status when a booking is submitted with a payment method outside of its recognized gateways. An unauthenticated attacker can send a specially crafted POST request specifying an arbitrary payment method and a status of 'approved' to bypass the payment processing logic. This results in the system confirming the booking, sending confirmation emails, and reserving calendar slots without any financial transaction occurring. The issue is fixed in version 1.0.57.
Affected products
- Timetics Timetics before 1.0.57
Timeline
- 2026-07-01: disclosed: Publicly published by WPScan
- 2026-07-22: advisory: CVE published to NVD
- 2026-07-22: patched: Fixed in version 1.0.57