wpdevart Booking Calendar Plugin up to 3.2.36 on WordPress authorization

Summaryinfo

A vulnerability was found in wpdevart Booking Calendar Plugin up to 3.2.36. It has been rated as critical. The affected element is an unknown function. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2026-57778. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in wpdevart Booking Calendar Plugin up to 3.2.36. This affects an unknown function. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Missing Authorization vulnerability in wpdevart Booking calendar, Appointment Booking System booking-calendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking calendar, Appointment Booking System: from n/a through <= 3.2.36.

The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-57778 since 06/25/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. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/13/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

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

Productinfo

Type

• WordPress Plugin

Vendor

• wpdevart

Name

• Booking Calendar Plugin

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9
• 3.2.10
• 3.2.11
• 3.2.12
• 3.2.13
• 3.2.14
• 3.2.15
• 3.2.16
• 3.2.17
• 3.2.18
• 3.2.19
• 3.2.20
• 3.2.21
• 3.2.22
• 3.2.23
• 3.2.24
• 3.2.25
• 3.2.26
• 3.2.27
• 3.2.28
• 3.2.29
• 3.2.30
• 3.2.31
• 3.2.32
• 3.2.33
• 3.2.34
• 3.2.35
• 3.2.36

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