BookingPress Plugin up to 1.0.74 on WordPress Price bookingpress_confirm_booking access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in BookingPress Plugin up to 1.0.74 on WordPress. Affected by this vulnerability is the function bookingpress_confirm_booking of the component Price Handler. This manipulation causes access control.
This vulnerability appears as CVE-2023-51405. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical was found in BookingPress Plugin up to 1.0.74 on WordPress (WordPress Plugin). Affected by this vulnerability is the function bookingpress_confirm_booking of the component Price Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity. The summary by CVE is:
Improper Authentication vulnerability in Repute Infosystems BookingPress allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects BookingPress: from n/a through 1.0.74.
The weakness was presented 01/05/2024. The advisory is shared at wordfence.com. This vulnerability is known as CVE-2023-51405 since 12/18/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 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.
Product
Type
Name
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/18/2023 🔍01/05/2024 🔍
01/05/2024 🔍
03/13/2025 🔍
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2023-51405 (🔍)
GCVE (CVE): GCVE-0-2023-51405
GCVE (VulDB): GCVE-100-249733
Entry
Created: 01/05/2024 09:20Updated: 03/13/2025 03:12
Changes: 01/05/2024 09:20 (39), 03/13/2025 03:12 (37)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.