# CVE-2023-2416: Online Booking & Scheduling Calendar for WordPress by vcita <= 4.5 - Cross-Site Request Forgery to Account Logout

> Attackers can force logged-in users to log out of their vcita accounts via CSRF, causing denial of service for the appointment scheduler.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jun 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hvfm-839j-xgqx

## What is CVE-2023-2416?

CVE-2023-2416 is a medium-severity vulnerability in Online Booking & Scheduling Calendar for WordPress by vcita, published on 3 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Online Booking & Scheduling Calendar for WordPress by vcita plugin for WordPress is vulnerable to Cross-Site Request Forgery due to a missing nonce check on the vcita_logout_callback function in versions up to, and including, 4.5. This makes it possible for unauthenticated to logout a vctia connected account which would cause a denial of service on the appointment scheduler, via a forged request granted they can trick a site user into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-2416?

It affects 1 product.


Products: Vcita Online Booking \& Scheduling Calendar.

## How do I fix CVE-2023-2416?

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

## Is CVE-2023-2416 being exploited?

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

## Other vulnerabilities in Online Booking & Scheduling Calendar for WordPress by vcita

- [CVE-2025-54677](https://insights.sbomify.com/CVE-2025-54677/): File upload in Online Booking & Scheduling Calendar for WordPress by vcita (critical 9.1)
- [CVE-2024-5791](https://insights.sbomify.com/CVE-2024-5791/): Cross-site scripting in Online Booking & Scheduling Calendar for WordPress by vcita (high 7.2)
- [CVE-2023-2298](https://insights.sbomify.com/CVE-2023-2298/): Online Booking & Scheduling Calendar for WordPress by vcita <= 4.3.0 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2024-47638](https://insights.sbomify.com/CVE-2024-47638/): Cross-site scripting in Online Booking & Scheduling Calendar for WordPress by vcita (high 7.1)
- [CVE-2024-37262](https://insights.sbomify.com/CVE-2024-37262/): WordPress Online Booking & Scheduling Calendar plugin <= 4.4.2 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2416 and fix it if it is affected.

What it is: CVE-2023-2416 is a medium-severity vulnerability in Online Booking & Scheduling Calendar for WordPress by vcita, published on 3 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-2416 in the wild and no public exploit code.

Affected product: Online Booking & Scheduling Calendar for WordPress by vcita. 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-2023-2416/ (Markdown: https://insights.sbomify.com/CVE-2023-2416/index.md)
```

## Sources

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

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