# CVE-2026-14215: Amelia < 2.4.9 - Unauthenticated Post-Booking Action Trigger

> Unauthenticated attackers can trigger booking notifications and integration callbacks by enumerating booking identifiers in the Amelia WordPress plugin.

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

## What is CVE-2026-14215?

CVE-2026-14215 is a medium-severity missing authorization vulnerability in Unknown Booking for Appointments and Events Calendar, published on 2 Sep 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  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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-14215 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14215 is a medium-severity missing authorization vulnerability in Unknown Booking for Appointments and Events Calendar, published on 2 Sep 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-14215 in the wild and no public exploit code.

Affected product: Unknown Booking for Appointments and Events Calendar. 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-14215/ (Markdown: https://insights.sbomify.com/CVE-2026-14215/index.md)
```

## Sources

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

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