# CVE-2026-100163: Auth bypass in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

> Attackers can hijack customer accounts by exploiting a username collision flaw in the LatePoint WordPress plugin when specific settings are enabled.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-fwf2-rqrw-2q37

## What is CVE-2026-100163?

CVE-2026-100163 is a high-severity authentication bypass vulnerability in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 5.7.2 via the OsCustomerHelper::create_wp_user_for_customer() helper reached from the public process_step_customer() booking step. When the 'Use WordPress users as customers' option is enabled, the helper falls back from email_exists() to username_exists( $customer->email ), which matches any WordPress user whose user_login equals the victim customer's email even when that user's user_email is completely different, and links that WordPress user's ID into the victim's LatePoint customer row (only privileged roles are excluded; Subscriber is allowed). This makes it possible for authenticated attackers, with Subscriber-level access and above, to take over another customer's LatePoint account — accessing their bookings, service, agent, and calendar data, and having the victim customer's email overwritten with the attacker's on next login — by holding a Subscriber account whose user_login equals the victim's email and submitting an unauthenticated public booking step registration request.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-100163 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100163 is a high-severity authentication bypass vulnerability in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, published on 14 Oct 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-100163 in the wild and no public exploit code.

Affected product: Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress. 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-100163/ (Markdown: https://insights.sbomify.com/CVE-2026-100163/index.md)
```

## Sources

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

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