TMS Booking for Appointments and Events Calendar Plugin cross site scripting

Summaryinfo

A vulnerability was found in TMS Booking for Appointments and Events Calendar Plugin up to 1.0.85 on WordPress. It has been rated as problematic. This issue affects some unknown processing. Performing a manipulation results in cross site scripting. This vulnerability is known as CVE-2023-50860. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as problematic has been found in TMS Booking for Appointments and Events Calendar Plugin up to 1.0.85 on WordPress (Calendar Software). This affects an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in TMS Booking for Appointments and Events Calendar – Amelia allows Stored XSS.This issue affects Booking for Appointments and Events Calendar – Amelia: from n/a through 1.0.85.

The weakness was published 12/28/2023. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2023-50860 since 12/14/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

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

• Calendar Software

Vendor

• TMS

Name

• Booking for Appointments and Events Calendar Plugin

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9
• 1.0.10
• 1.0.11
• 1.0.12
• 1.0.13
• 1.0.14
• 1.0.15
• 1.0.16
• 1.0.17
• 1.0.18
• 1.0.19
• 1.0.20
• 1.0.21
• 1.0.22
• 1.0.23
• 1.0.24
• 1.0.25
• 1.0.26
• 1.0.27
• 1.0.28
• 1.0.29
• 1.0.30
• 1.0.31
• 1.0.32
• 1.0.33
• 1.0.34
• 1.0.35
• 1.0.36
• 1.0.37
• 1.0.38
• 1.0.39
• 1.0.40
• 1.0.41
• 1.0.42
• 1.0.43
• 1.0.44
• 1.0.45
• 1.0.46
• 1.0.47
• 1.0.48
• 1.0.49
• 1.0.50
• 1.0.51
• 1.0.52
• 1.0.53
• 1.0.54
• 1.0.55
• 1.0.56
• 1.0.57
• 1.0.58
• 1.0.59
• 1.0.60
• 1.0.61
• 1.0.62
• 1.0.63
• 1.0.64
• 1.0.65
• 1.0.66
• 1.0.67
• 1.0.68
• 1.0.69
• 1.0.70
• 1.0.71
• 1.0.72
• 1.0.73
• 1.0.74
• 1.0.75
• 1.0.76
• 1.0.77
• 1.0.78
• 1.0.79
• 1.0.80
• 1.0.81
• 1.0.82
• 1.0.83
• 1.0.84
• 1.0.85

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