# CVE-2026-9232: Missing authorization in Easy Appointments

> Authenticated contributors can access sensitive customer PII due to missing authorization checks in the Easy Appointments WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-m6cm-g8vp-fpwm

## What is CVE-2026-9232?

CVE-2026-9232 is a medium-severity missing authorization vulnerability in easyappointments Easy Appointments, published on 19 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Easy Appointments plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.12.27 via the handle_customers_ajax. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the full customer dataset from the ea_customers table, including personally identifiable information such as names, email addresses, mobile numbers, dates of birth, and physical addresses.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-9232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9232 is a medium-severity missing authorization vulnerability in easyappointments Easy Appointments, published on 19 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9232 in the wild and no public exploit code.

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

## Sources

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

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