Appointment Booking Calendar Plugin up to 1.6.6.20 on WordPress Plugin Data Reset cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Appointment Booking Calendar Plugin up to 1.6.6.20 on WordPress. Affected by this issue is some unknown functionality of the component Plugin Data Reset Handler. This manipulation causes cross-site request forgery. This vulnerability is tracked as CVE-2024-1760. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in Appointment Booking Calendar Plugin up to 1.6.6.20 on WordPress (Appointment Software). Affected by this vulnerability is some unknown functionality of the component Plugin Data Reset Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:
The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6.6.20. This is due to missing or incorrect nonce validation on the ssa_factory_reset() function. This makes it possible for unauthenticated attackers to reset the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
The weakness was disclosed 03/05/2024. The advisory is shared at wordfence.com. This vulnerability is known as CVE-2024-1760 since 02/22/2024. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 1.6.6.0
- 1.6.6.1
- 1.6.6.2
- 1.6.6.3
- 1.6.6.4
- 1.6.6.5
- 1.6.6.6
- 1.6.6.7
- 1.6.6.8
- 1.6.6.9
- 1.6.6.10
- 1.6.6.11
- 1.6.6.12
- 1.6.6.13
- 1.6.6.14
- 1.6.6.15
- 1.6.6.16
- 1.6.6.17
- 1.6.6.18
- 1.6.6.19
- 1.6.6.20
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.7
NVD Vector: 🔍
CNA Base Score: 4.3
CNA Vector (Wordfence): 🔍
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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
02/22/2024 🔍03/05/2024 🔍
03/05/2024 🔍
04/12/2026 🔍
Sources
Advisory: 3042890Status: Not defined
CVE: CVE-2024-1760 (🔍)
GCVE (CVE): GCVE-0-2024-1760
GCVE (VulDB): GCVE-100-255817
Entry
Created: 03/05/2024 21:02Updated: 04/12/2026 17:29
Changes: 03/05/2024 21:02 (38), 04/04/2024 21:21 (16), 04/04/2024 21:30 (10), 04/17/2025 22:47 (4), 04/12/2026 17:29 (13)
Complete: 🔍
Cache ID: 216:B24:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.