CVE-2026-16582

Booking for Appointments and Events Calendar - Amelia <= 2.4.5 - Missing Authorization to Unauthenticated Payment Bypass

2026-09-17 09:08
ricky morty

Strategic Overview

Status
Patched in 2.4.6
Affected Version
<= 2.4.5
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-16582
View all Booking for Appointments and Events Calendar – Amelia vulnerabilities

At a glance

CVE-2026-16582 is a medium-severity Missing Authorization vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions <= 2.4.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.6; sites on affected versions should update now. Disclosed September 2026, reported by ricky morty.

Vulnerability Overview

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to unauthorized modification of data in all versions up to, and including, 2.4.5. This is due to the plugin accepting a client-supplied package-redemption identifier as proof of payment without validating it. This makes it possible for unauthenticated attackers to create approved appointment bookings without completing payment

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Booking for Appointments and Events Calendar <= 2.4.5 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Booking for Appointments and Events Calendar the fix is 2.4.6: builds <= 2.4.5 are affected, anything from 2.4.6 onward is not.

Remediation

Update to version 2.4.6, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Booking for Appointments and Events Calendar 2.4.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C