Skip to main content

Timetics WordPress Plugin CVE-2026-14322

| EUVDEUVD-2026-47614 MEDIUM
Improper Access Control (CWE-284)
2026-07-22 WPScan GHSA-4m7v-hj47-rqcr
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site with Timetics plugin
  2. Delivery
    Submit booking for priced appointment slot
  3. Exploit
    Specify unrecognized payment method in request
  4. Execution
    Plugin skips payment validation
  5. Persist
    Booking approved without payment
  6. Impact
    Repeat to exhaust merchant calendar

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No authentication is required (PR:N confirmed by CVSS vector AV:N/AC:L/PR:N/UI:N). The sole prerequisite is that the target WordPress site has the Timetics plugin installed at a version below 1.0.57 with at least one priced appointment type configured. The bypass is triggered specifically when a booking is submitted using a payment method not in Timetics' recognized gateway list - if a site only offers recognized gateways and enforces selection, the attack surface may be narrowed, but this is a configuration-dependent mitigating factor rather than a reliable control. No special network position, account, or platform is required. Exploitation is limited to the booking integrity impact only; no confidentiality or availability impact is achievable through this vector.

Impact

The CVSS 3.1 score of 5.3 (Medium, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) accurately captures the limited blast radius: no data is exposed and no service is disrupted, but unauthorized write operations (approved bookings without payment) corrupt business logic. EPSS at 0.14% (4th percentile) indicates very low exploitation probability in the broader threat landscape, which partially contradicts the SSVC finding that the flaw is 'automatable' - this discrepancy suggests that while automated exploitation is technically feasible, the narrow deployment footprint of Timetics keeps real-world risk contained. A public POC exists (via WPScan), elevating urgency above the EPSS signal alone. KEV status is not confirmed, so this is not known to be actively exploited at scale. The primary real-world risk is financial: attackers can book paid appointment slots at no cost, causing revenue loss and calendar disruption for businesses running this plugin. SSVC Technical Impact is rated 'partial', consistent with integrity-only impact.

Exploit ScenarioDerived

An attacker identifies a WordPress site using Timetics with priced appointment bookings by scanning for plugin-specific endpoints or checking publicly visible booking pages. They submit a booking request for a paid appointment slot, selecting or specifying a payment method not in the plugin's recognized gateway list, which causes the server to skip payment validation and mark the booking as fully approved. The attacker repeats this process automatically - the SSVC confirms automatable - to fill the merchant's calendar with free bookings, blocking legitimate paying customers and causing direct revenue loss.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 22, 2026

Payment enforcement bypass in the Timetics WordPress booking plugin (versions before 1.0.57) allows unauthenticated remote users to generate fully-approved appointments for priced services without completing any payment. The plugin fails to validate booking status when the chosen payment method falls outside its recognized gateway list, effectively treating unverified payment submissions as completed transactions. A public proof-of-concept is available (reported by WPScan), and SSVC assessment confirms the flaw is automatable with partial technical impact, though EPSS remains low at 0.14%, suggesting exploitation is opportunistic rather than widespread.

RemediationAI

The primary fix is to update the Timetics plugin to version 1.0.57 or later, which enforces proper booking status validation regardless of the submitted payment method. The patch is confirmed available from the vendor per WPScan (https://wpscan.com/vulnerability/0fb14dca-d4aa-4c24-bf15-37099edb7614/) and referenced via VulnDB advisory https://vuldb.com/vuln/382259. If immediate upgrade is not possible, administrators should temporarily disable the booking form for priced appointments or restrict access to the booking endpoint to authenticated users only via a WAF or WordPress access control plugin. Alternatively, disabling the ability to select non-recognized payment gateways at checkout (if configurable) would eliminate the bypass path, though this may reduce functionality for legitimate users. Site owners should audit existing bookings created after the plugin was installed to identify fraudulently approved reservations and reverse them manually.

Affected VersionsENISA

Timetics 0 <1.0.57

Affected Packages

euvd timetics fix: 1.0.57

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Timetics is a WordPress appointment and booking plugin. The vulnerability stems from CWE-284 (Improper Access Control) in the booking creation workflow. Specifically, the plugin's server-side logic does not enforce a 'pending' or 'unpaid' status guard when a booking is submitted via a payment method not included in the plugin's recognized gateway list. Instead of defaulting to an unconfirmed state pending payment verification, the booking is transitioned directly to a fully-approved status. The affected CPE is cpe:2.3:a:unknown:timetics:*:*:*:*:*:*:*:* covering all versions prior to 1.0.57. The root cause is a missing state-machine check at the payment-method branching point in booking creation logic, a classic authorization bypass rather than a cryptographic or injection flaw.

Know when Timetics gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 5.3 MEDIUM

Network-accessible, no auth required, low integrity impact only; no confidentiality or availability impact from booking fraud.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

4
CVSS changed
Jul 22, 2026 - 16:22 NVD
5.3 (None) 5.3 (MEDIUM)
Patch available
Jul 22, 2026 - 08:47 EUVD
CVE Published
Jul 22, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 22, 2026 - 06:00 cve.org
MEDIUM 5.3

DescriptionCVE.org

The Timetics WordPress plugin before 1.0.57 does not enforce a pending or unpaid status for new bookings created through a payment method other than its recognised gateways, allowing unauthenticated users to create fully-approved bookings for priced appointments without making any payment.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Low
niche WordPress booking plugin, limited enterprise footprint
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy