Show filters
7 Total Results
Displaying 1-7 of 7
Sort by:
Attacker Value
Unknown
CVE-2022-45824
Disclosure Date: December 05, 2022 (last updated February 24, 2025)
Cross-Site Request Forgery (CSRF) vulnerability in Advanced Booking Calendar plugin <= 1.7.1 on WordPress.
0
Attacker Value
Unknown
CVE-2022-45822
Disclosure Date: December 05, 2022 (last updated February 24, 2025)
Unauth. SQL Injection (SQLi) vulnerability in Advanced Booking Calendar plugin <= 1.7.1 on WordPress.
0
Attacker Value
Unknown
CVE-2022-1007
Disclosure Date: April 11, 2022 (last updated February 23, 2025)
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
0
Attacker Value
Unknown
CVE-2022-1006
Disclosure Date: April 11, 2022 (last updated February 23, 2025)
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
0
Attacker Value
Unknown
CVE-2022-0694
Disclosure Date: March 21, 2022 (last updated February 23, 2025)
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
0
Attacker Value
Unknown
CVE-2021-24232
Disclosure Date: April 22, 2021 (last updated February 22, 2025)
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
0
Attacker Value
Unknown
CVE-2021-24225
Disclosure Date: April 12, 2021 (last updated February 22, 2025)
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
0