Appointment Hour Booking Plugin up to 1.5.87 on WordPress improper authentication

Summaryinfo

A vulnerability classified as critical has been found in Appointment Hour Booking Plugin up to 1.5.87. The impacted element is an unknown function. Performing a manipulation results in improper authentication. This vulnerability is identified as CVE-2026-16282. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Appointment Hour Booking Plugin up to 1.5.87. It has been classified as critical. This affects some unknown processing. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on integrity, and availability. The summary by CVE is:

The Appointment Hour Booking WordPress plugin before 1.5.88 does not validate a client-supplied booking price against the server-side configured service price, allowing unauthenticated users to submit an arbitrary final price (including zero or negative) that is stored as the authoritative booking price, corrupting booking and payment records.

The advisory is shared at wpscan.com. This vulnerability is uniquely identified as CVE-2026-16282 since 07/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.5.88 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Name

• Appointment Hour Booking Plugin

Version

• 1.5.0
• 1.5.1
• 1.5.2
• 1.5.3
• 1.5.4
• 1.5.5
• 1.5.6
• 1.5.7
• 1.5.8
• 1.5.9
• 1.5.10
• 1.5.11
• 1.5.12
• 1.5.13
• 1.5.14
• 1.5.15
• 1.5.16
• 1.5.17
• 1.5.18
• 1.5.19
• 1.5.20
• 1.5.21
• 1.5.22
• 1.5.23
• 1.5.24
• 1.5.25
• 1.5.26
• 1.5.27
• 1.5.28
• 1.5.29
• 1.5.30
• 1.5.31
• 1.5.32
• 1.5.33
• 1.5.34
• 1.5.35
• 1.5.36
• 1.5.37
• 1.5.38
• 1.5.39
• 1.5.40
• 1.5.41
• 1.5.42
• 1.5.43
• 1.5.44
• 1.5.45
• 1.5.46
• 1.5.47
• 1.5.48
• 1.5.49
• 1.5.50
• 1.5.51
• 1.5.52
• 1.5.53
• 1.5.54
• 1.5.55
• 1.5.56
• 1.5.57
• 1.5.58
• 1.5.59
• 1.5.60
• 1.5.61
• 1.5.62
• 1.5.63
• 1.5.64
• 1.5.65
• 1.5.66
• 1.5.67
• 1.5.68
• 1.5.69
• 1.5.70
• 1.5.71
• 1.5.72
• 1.5.73
• 1.5.74
• 1.5.75
• 1.5.76
• 1.5.77
• 1.5.78
• 1.5.79
• 1.5.80
• 1.5.81
• 1.5.82
• 1.5.83
• 1.5.84
• 1.5.85
• 1.5.86
• 1.5.87

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion