Booking for Appointments and Events Calendar – Amelia vulnerabilities
Plugin slug ameliabooking · 57 known vulnerabilities · latest disclosed 2026-11-06 · WordPress.org page
Every listed vulnerability has a fix. Version 9.9.2 or later is not affected by any of them. If your site runs an older version, update it.
13 of 57 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Booking for Appointments and Events Calendar – Amelia
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.5 | 9.0 to 9.9.1 | 9.9.2 | CVE-2026-107616 | 2026-11-06 | Advisory |
| Medium 6.5 | 9.0 to 9.9.1 | 9.9.2 | CVE-2026-104992 | 2026-11-06 | Advisory |
| Medium 5.3 | <= 2.4.12 | 2.4.13 | CVE-2026-103915 | 2026-10-30 | Advisory |
| Medium 5.3 | <= 2.4.10 | 2.4.11 | CVE-2026-116388 | 2026-10-26 | Advisory |
| Medium 6.4 | <= 2.4.12 | 2.4.13 | CVE-2026-116396 | 2026-10-26 | Advisory |
| High 7.5 | <= 2.4.11 | 2.4.12 | CVE-2026-112327 | 2026-10-20 | Advisory |
| High 7.5 | <= 2.4.10 | 2.4.11 | CVE-2026-108497 | 2026-10-13 | Advisory |
| Medium 5.3 | <= 2.4.10 | 2.4.11 | CVE-2026-109684 | 2026-10-13 | Advisory |
| Medium 5.3 | <= 2.4.10 | 2.4.11 | CVE-2026-96461 | 2026-10-02 | Advisory |
| Medium 5.4 | <= 2.4.4 | 2.4.5 | CVE-2026-14311 | 2026-09-17 | Advisory |
| Medium 5.3 | <= 2.4.5 | 2.4.6 | CVE-2026-16582 | 2026-09-17 | Advisory |
| Medium 6.3 | < 2.4.10 | 2.4.10 | CVE-2026-77705 | 2026-09-14 | Advisory |
| Medium 6.4 | <= 2.4.9 | 2.4.10 | CVE-2026-10148 | 2026-09-11 | Advisory |
| Medium 4.9 | <= 2.4.9 | 2.4.10 | CVE-2026-62112 | 2026-09-11 | Advisory |
| Medium 5.3 | 9.0 to 9.8.0 | 9.8.1 | CVE-2026-77689 | 2026-09-10 | Advisory |
| Critical 9.8 | 8.0 to 9.6.2 | 9.6.3 | CVE-2026-9055 | 2026-09-01 | Advisory |
| Medium 5.3 | < 2.4.9 | 2.4.9 | CVE-2026-14215 | 2026-08-31 | Advisory |
| Medium 4.3 | 1.2.32 to 2.4.8 | 2.4.9 | CVE-2026-77704 | 2026-08-29 | Advisory |
| Medium 6.3 | 9.0 to 9.7 | 9.8 | CVE-2026-14212 | 2026-08-28 | Advisory |
| High 7.2 | <= 2.2 | 2.2.1 | CVE-2026-6286 | 2026-08-27 | Advisory |
| Medium 5.3 | < 2.4.7 | 2.4.7 | CVE-2026-14216 | 2026-08-26 | Advisory |
| Medium 4.3 | < 2.4.6 | 2.4.6 | CVE-2026-14213 | 2026-08-14 | Advisory |
| Medium 4.3 | <= 9.6 | 9.7 | CVE-2026-14211 | 2026-08-07 | Advisory |
| Medium 4.3 | < 2.4.4 | 2.4.4 | CVE-2026-14214 | 2026-08-01 | Advisory |
| Medium 4.9 | <= 2.4.3 | 2.4.4 | CVE-2026-14782 | 2026-07-16 | Advisory |
| High 7.5 | <= 2.4.2 | 2.4.3 | CVE-2026-57702 | 2026-07-08 | Advisory |
| High 8.8 | <= 2.3 | 2.4 | CVE-2026-48889 | 2026-06-02 | Advisory |
| Medium 5.3 | <= 2.2.1 | 2.3 | CVE-2026-6449 | 2026-05-01 | Advisory |
| Medium 4.3 | <= 2.2 | 2.2.1 | CVE-2026-40795 | 2026-04-28 | Advisory |
| Medium 5.3 | <= 2.2 | 2.2.1 | CVE-2026-40789 | 2026-04-23 | Advisory |
| High 8.8 | <= 2.1.3 | 2.2 | CVE-2026-5465 | 2026-04-06 | Advisory |
| Medium 6.5 | <= 2.1.2 | 2.1.3 | CVE-2026-4668 | 2026-03-31 | Advisory |
| High 8.8 | 8.3 to 9.1.2 | 9.2 | CVE-2026-2931 | 2026-03-25 | Advisory |
| Medium 6.5 | <= 2.1.1 | 2.1.2 | CVE-2026-39487 | 2026-03-25 | Advisory |
| High 8.8 | <= 1.2.38 | 2.0 | CVE-2026-24963 | 2026-03-04 | Advisory |
| Medium 5.3 | <= 1.2.38 | 2.0 | CVE-2026-24967 | 2026-01-11 | Advisory |
| Medium 5.3 | <= 1.2.38 | 2.0.0 | CVE-2025-14720 | 2026-01-08 | Advisory |
| Medium 5.3 | 1.2.18 to 1.2.36 | 1.2.37 | CVE-2023-49282 | 2025-11-18 | Advisory |
| High 7.5 | <= 1.2.35 | 1.2.36 | CVE-2025-12482 | 2025-11-15 | Advisory |
| Medium 5.3 | <= 1.2.19 | 1.2.20 | CVE-2025-2578 | 2025-03-27 | Advisory |
| Medium 5.3 | <= 1.2.16 | 1.2.17 | CVE-2025-26965 | 2025-02-23 | Advisory |
| Medium 6.5 | <= 1.2.4 | 1.2.5 | CVE-2024-6332 | 2024-09-04 | Advisory |
| Medium 5.3 | <= 1.2 | 1.2.1 | CVE-2024-6552 | 2024-08-07 | Advisory |
| Medium 4.4 | <= 1.1.5 | 1.1.6 | CVE-2024-6225 | 2024-06-20 | Advisory |
| Medium 4.3 | <= 1.0.95 | 1.0.96 | CVE-2024-31425 | 2024-04-10 | Advisory |
| Medium 6.1 | <= 1.0.98 | 1.0.99 | CVE-2024-1484 | 2024-02-29 | Advisory |
| Medium 6.4 | <= 1.0.93 | 1.0.94 | CVE-2023-6808 | 2024-01-18 | Advisory |
| Medium 6.5 | <= 1.0.98 | 1.0.99 | CVE-2024-22298 | 2024-01-17 | Advisory |
| Medium 6.4 | <= 1.0.85 | 1.0.86 | CVE-2023-50860 | 2023-12-22 | Advisory |
| Medium 6.1 | <= 1.0.75 | 1.0.76 | CVE-2023-29427 | 2023-04-06 | Advisory |
| Medium 5.4 | < 1.0.49 | 1.0.49 | CVE-2022-0825 | 2022-03-14 | Advisory |
| Medium 6.4 | < 1.0.48 | 1.0.48 | CVE-2022-0837 | 2022-03-14 | Advisory |
| High 7.2 | <= 1.0.46 | 1.0.47 | CVE-2022-0834 | 2022-03-02 | Advisory |
| Medium 5.4 | < 1.0.47 | 1.0.47 | CVE-2022-0720 | 2022-03-01 | Advisory |
| Medium 4.3 | <= 1.0.46 | 1.0.47 | CVE-2022-0616 | 2022-02-23 | Advisory |
| Medium 6.1 | <= 1.0.46 | 1.0.47 | CVE-2022-0627 | 2022-02-23 | Advisory |
| High 8.8 | < 1.0.47 | 1.0.47 | CVE-2022-0687 | 2022-02-23 | Advisory |
Check if a site is affected
Enter a site address to see which version of Booking for Appointments and Events Calendar – Amelia and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Booking for Appointments and Events Calendar – Amelia plugin safe to use?
All 57 known issues are fixed in current versions (9.9.2 or later). Keeping it updated is what matters.
How do I check which version of Booking for Appointments and Events Calendar – Amelia my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.
Check any WordPress site in one click while you browse: Add PluginPeek to Chrome