# CVE-2026-6449: Auth bypass in Booking for Appointments and Events Calendar – Amelia

> Unauthenticated attackers can bypass authorization to approve waiting bookings via the admin-ajax endpoint, requiring plugin updates.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-w8hw-gcrw-wj77

## What is CVE-2026-6449?

CVE-2026-6449 is a medium-severity authentication bypass vulnerability in ameliabooking Booking for Appointments and Events Calendar – Amelia, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Improper Authorization in all versions up to, and including, 2.1.2. This is due to a logical short-circuit flaw in authorization logic that causes token validation to be entirely skipped when a booking has a 'waiting' status. This makes it possible for unauthenticated attackers to approve any booking that is in 'waiting' status by sending a crafted request to the publicly-accessible admin-ajax endpoint.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-6449?


## How do I fix CVE-2026-6449?

No fix has been published for CVE-2026-6449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6449 being exploited?

There is no known exploitation of CVE-2026-6449 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6449 and fix it if it is affected.

What it is: CVE-2026-6449 is a medium-severity authentication bypass vulnerability in ameliabooking Booking for Appointments and Events Calendar – Amelia, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6449 in the wild and no public exploit code.

Affected product: ameliabooking Booking for Appointments and Events Calendar – Amelia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6449/ (Markdown: https://insights.sbomify.com/CVE-2026-6449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6449
- OSV: https://osv.dev/vulnerability/CVE-2026-6449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6449/
Summaries are generated and may contain mistakes; the official description above is the record.