Filtered by vendor Elbtide
Subscribe
Total
7 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2022-45824 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | N/A | 6.5 MEDIUM |
| Cross-Site Request Forgery (CSRF) vulnerability in Advanced Booking Calendar plugin <= 1.7.1 on WordPress. | |||||
| CVE-2022-45822 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | N/A | 9.8 CRITICAL |
| Unauth. SQL Injection (SQLi) vulnerability in Advanced Booking Calendar plugin <= 1.7.1 on WordPress. | |||||
| CVE-2022-1006 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | 6.5 MEDIUM | 7.2 HIGH |
| The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the id parameter when editing Calendars, which could allow high privilege users such as admin to perform SQL injection attacks | |||||
| CVE-2022-1007 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | 4.3 MEDIUM | 6.1 MEDIUM |
| The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the room parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting issue | |||||
| CVE-2022-0694 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | 7.5 HIGH | 9.8 CRITICAL |
| The Advanced Booking Calendar WordPress plugin before 1.7.0 does not validate and escape the calendar parameter before using it in a SQL statement via the abc_booking_getSingleCalendar AJAX action (available to both unauthenticated and authenticated users), leading to an unauthenticated SQL injection | |||||
| CVE-2021-24232 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | 3.5 LOW | 5.4 MEDIUM |
| The Advanced Booking Calendar WordPress plugin before 1.6.8 does not sanitise the license error message when output in the settings page, leading to an authenticated reflected Cross-Site Scripting issue | |||||
| CVE-2021-24225 | 1 Elbtide | 1 Advanced Booking Calendar | 2024-02-28 | 3.5 LOW | 5.4 MEDIUM |
| The Advanced Booking Calendar WordPress plugin before 1.6.7 did not sanitise the calId GET parameter in the "Seasons & Calendars" page before outputing it in an A tag, leading to a reflected XSS issue | |||||