# CVE-2026-3045: Missing authorization in Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin

> Unauthenticated attackers can access sensitive admin settings and modify appointments due to missing authorization checks in the REST API.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 13 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-4w38-6pqj-mw46

## What is CVE-2026-3045?

CVE-2026-3045 is a high-severity missing authorization vulnerability in croixhaug Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Appointment Booking Calendar — Simply Schedule Appointments plugin for WordPress is vulnerable to unauthorized access of sensitive data in all versions up to and including 1.6.9.29. This is due to two compounding weaknesses: (1) a non-user-bound `public_nonce` is exposed to unauthenticated users through the public `/wp-json/ssa/v1/embed-inner` REST endpoint, and (2) the `get_item()` method in `SSA_Settings_Api` relies on `nonce_permissions_check()` for authorization (which accepts the public nonce) but does not call `remove_unauthorized_settings_for_current_user()` to filter restricted fields. This makes it possible for unauthenticated attackers to access admin-only plugin settings including the administrator email, phone number, internal access tokens, notification configurations, and developer settings via the `/wp-json/ssa/v1/settings/{section}` endpoint. The exposure of appointment tokens also allows an attacker to modify or cancel appointments.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-3045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3045 is a high-severity missing authorization vulnerability in croixhaug Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin, published on 13 Mar 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-3045 in the wild and no public exploit code.

Affected product: croixhaug Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin. 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-3045/ (Markdown: https://insights.sbomify.com/CVE-2026-3045/index.md)
```

## Sources

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

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