# CVE-2024-10856: Booking Calendar WpDevArt <= 3.2.19 - Authenticated (Contributor+) SQL Injection

> Authenticated contributors can exploit SQL injection in the Booking Calendar plugin to extract sensitive database information when a specific theme option is enabled.

- **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:** 24 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-cq77-jhpm-mjmj

## What is CVE-2024-10856?

CVE-2024-10856 is a medium-severity SQL injection vulnerability in wpdevart Booking calendar, Appointment Booking System, published on 24 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Booking Calendar WpDevArt plugin is vulnerable to time-based, blind SQL injection via the `id` parameter in the “wpdevart_booking_calendar” shortcode in versions up to, and including, 3.2.19 due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query. The vulnerability requires the “delete_prev_date” theme option being enabled. This makes it possible for authenticated attackers, with contributor-level access or above, to append additional SQL queries into already existing query that can be used to extract sensitive information such as passwords from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-10856?

It affects 1 product.


Products: Wpdevart Booking Calendar.

## How do I fix CVE-2024-10856?

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

## Is CVE-2024-10856 being exploited?

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

## Other vulnerabilities in wpdevart Booking calendar, Appointment Booking System

- [CVE-2022-3982](https://insights.sbomify.com/CVE-2022-3982/): Booking Calendar < 3.2.2 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2018-10363](https://insights.sbomify.com/CVE-2018-10363/): Business logic in n/a (high 7.5)
- [CVE-2022-47428](https://insights.sbomify.com/CVE-2022-47428/): WordPress Booking calendar, Appointment Booking System Plugin <= 3.2.7 is vulnerable to SQL Injection (medium 6.7)
- [CVE-2022-47438](https://insights.sbomify.com/CVE-2022-47438/): WordPress Booking calendar, Appointment Booking System Plugin <= 3.2.3 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2023-24388](https://insights.sbomify.com/CVE-2023-24388/): Cross-site request forgery in Booking calendar, Appointment Booking System (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10856 and fix it if it is affected.

What it is: CVE-2024-10856 is a medium-severity SQL injection vulnerability in wpdevart Booking calendar, Appointment Booking System, published on 24 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10856 in the wild and no public exploit code.

Affected product: wpdevart Booking calendar, Appointment Booking System. 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-2024-10856/ (Markdown: https://insights.sbomify.com/CVE-2024-10856/index.md)
```

## Sources

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

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