Is appointment-booking-calendar (WordPress plugin) vulnerable?

WordPress appointment-booking-calendar has 9 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

9advisories
1critical
0on CISA KEV
3no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2020-9372The Appointment Booking Calendar plugin before 1.3.35 for WordPress allows user input (in fields such as Description or Name) in any bookinghigh7.8<1.3.351.3.35
CVE-2020-9371Stored XSS exists in the Appointment Booking Calendar plugin before 1.3.35 for WordPress. In the cpabc_appointments.php file, the Calendar Nmedium4.8<1.3.351.3.35
CVE-2015-7319SQL injection vulnerability in cpabc_appointments_admin_int_calendar_list.inc.php in the Appointment Booking Calendar plugin before 1.1.8 fohigh7.5<=1.1.7–
CVE-2015-7320Multiple cross-site scripting (XSS) vulnerabilities in cpabc_appointments_admin_int_bookings_list.inc.php in the Appointment Booking Calendamedium4.3<=1.1.7–
CVE-2016-10916The appointment-booking-calendar plugin before 1.1.24 for WordPress has SQL injection, a different vulnerability than CVE-2015-7319.critical9.8<1.1.241.1.24
CVE-2019-14791The Appointment Booking Calendar plugin 1.3.18 for WordPress allows XSS via the wp-admin/admin-post.php editionarea parameter.medium6.1=1.3.18–
CVE-2024-12274The Appointment Booking Calendar Plugin and Scheduling Plugin WordPress plugin before 1.1.23 export settings functionality exports data to high7.5<1.1.231.1.23
CVE-2022-43482Missing Authorization vulnerability in Appointment Booking Calendar plugin <= 1.3.69 on WordPress.medium4.3<1.3.701.3.70
CVE-2024-0856The Appointment Booking Calendar WordPress plugin before 1.3.83 does not have CSRF checks in some places, which could allow attackers to makhigh8.8<1.3.831.3.83

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.