Amelia permits unauthenticated replay of post-booking actions
Amelia before 2.4.9 does not require authentication or a valid request token before running its post-booking action chain. An unauthenticated visitor who enumerates a booking ID can trigger its notification and integration callbacks.
- Component
- Booking for Appointments and Events Calendar
- Plugin slug
ameliabooking- Affected
- < 2.4.9
- Safe version
2.4.9- Published
- Sep 02, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Sep 02, 2026 and is one of 28 known issues for this plugin.
Update, patch or deactivate.
Update to Amelia 2.4.9 or later and review booking notifications and integration activity for unexpected replays.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.9 does not require authentication or a valid request token before running the post-booking action chain, allowing an unauthenticated user to trigger booking notifications and integration callbacks for a booking by enumerating its identifier.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L