WordPress plugin · appointment-booking-calendar
Is Appointment Booking Calendar safe?
A flaw affects the current version.
The newest release on wordpress.org, 1.4.07, is inside the affected range of CVE-2024-7129, so there may be no fix yet. Check the changelog; if it doesn’t mention the fix, deactivate it until it does.
- Flaws on record
- 16
- High or critical
- 6
- Exploited
- none
- Current version
- 1.4.07
- Last updated
- Oct 26, 2026
- Active installs
- 1,000+
Every recorded flaw
- Oct 28, 2026Appointment Booking Calendar: Stored Cross-Site ScriptingCVE-2026-111727 · affects up to 1.4.05 · reported by WordfenceMedium 6.4
- Jul 1, 2026Appointment Booking Calendar: Sensitive Information ExposureCVE-2026-12113 · affects up to 1.4.02 · reported by WordfenceMedium 4.3
- Jun 18, 2026Appointment Booking Calendar: Sensitive Information ExposureCVE-2026-12111 · affects up to 1.4.01 · reported by WordfenceMedium 4.3
- Nov 22, 2025Appointment Booking Calendar: Missing AuthorizationCVE-2025-13317 · affects up to 1.3.96 · reported by WordfenceMedium 5.3
- Nov 13, 2025Appointment Booking Calendar: Missing AuthorizationCVE-2025-64261 · affects up to 1.3.95 · reported by PatchstackMedium 5.4
- Apr 22, 2025Appointment Booking Calendar: Missing AuthorizationCVE-2025-46247 · affects up to 1.3.92 · reported by PatchstackMedium 5.3
- Apr 22, 2025Appointment Booking Calendar: Cross-Site Request Forgery (CSRF)CVE-2025-46241 · affects up to 1.3.92 · reported by PatchstackHigh 8.2
- Sep 13, 2024Appointment Booking Calendar: Does not escape template syntax provided via user inputCVE-2024-7129 · fixed in 1.6.7.43 · reported by WPScan1.1% oddsHigh 7.2
- Mar 20, 2024Appointment Booking Calendar: Does not have CSRF checks in some placesCVE-2024-0856 · fixed in 1.3.83 · reported by WPScanHigh 8.8
- Nov 18, 2022Missing Authorization vulnerability in Appointment Booking Calendar plugin <= 1.3.69 on WordPress.CVE-2022-43482 · affects up to 1.3.69 · reported by PatchstackMedium 4.3
- Mar 4, 2020The Appointment Booking Calendar plugin before 1.3.35 for WordPress allows user input (in fields such as Description or Name) in any booking form to be any formCVE-2020-9372 · fixed in 1.3.35 · reported by MITRE8.6% oddsHigh 7.8
- Mar 4, 2020Stored XSS exists in the Appointment Booking Calendar plugin before 1.3.35 for WordPress.CVE-2020-9371 · fixed in 1.3.35 · reported by MITRE3.3% oddsMedium 4.8
- Aug 22, 2019The appointment-booking-calendar plugin before 1.1.24 for WordPress has SQL injection, a different vulnerability than CVE-2015-7319.CVE-2016-10916 · fixed in 1.1.24 · reported by MITRE1.8% oddsCritical 9.8
- Aug 9, 2019The Appointment Booking Calendar plugin 1.3.18 for WordPress allows XSS via the wp-admin/admin-post.php editionarea parameter.CVE-2019-14791 · affects 1.3.18 to 1.3.18 · reported by MITRE1.4% oddsMedium 6.1
- Sep 29, 2015Multiple cross-site scripting (XSS) vulnerabilities in cpabc_appointments_admin_int_bookings_list.inc.php in the Appointment Booking Calendar plugin before 1.1.CVE-2015-7320 · fixed in 1.1.8 · reported by MITRE2.1% oddsMedium 4.3
- Sep 29, 2015SQL injection vulnerability in cpabc_appointments_admin_int_calendar_list.inc.php in the Appointment Booking Calendar plugin before 1.1.8 for WordPress allows rCVE-2015-7319 · fixed in 1.1.8 · reported by MITRE2.4% oddsHigh 7.5
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.