# CVE-2026-14222: Easy Appointments < 3.12.28 - Contributor+ Connection Deletion via Missing Authorization

> Contributor-level users can delete booking configurations due to missing authorization checks, disabling the booking system.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-hc6v-wvgv-hh32

## What is CVE-2026-14222?

CVE-2026-14222 is a low-severity missing authorization vulnerability in Unknown Easy Appointments, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Easy Appointments WordPress plugin before 3.12.28 does not perform any capability or nonce check in one of its connection-deletion actions, allowing users with contributor-level access to delete the booking configuration and disable the booking system.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-14222 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14222 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14222 is a low-severity missing authorization vulnerability in Unknown Easy Appointments, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14222 exists.

Affected product: Unknown Easy Appointments. 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-14222/ (Markdown: https://insights.sbomify.com/CVE-2026-14222/index.md)
```

## Sources

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

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