# CVE-2022-0739: BookingPress < 1.0.11 - Unauthenticated SQL Injection

> Unauthenticated attackers can inject SQL commands via the bookingpress_front_get_category_services AJAX action to read or modify database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rgvw-rx29-9j22

## What is CVE-2022-0739?

CVE-2022-0739 is a critical SQL injection vulnerability in Unknown BookingPress – Appointments Booking Calendar Plugin and Online Scheduling Plugin, published on 21 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BookingPress WordPress plugin before 1.0.11 fails to properly sanitize user supplied POST data before it is used in a dynamically constructed SQL query via the bookingpress_front_get_category_services AJAX action (available to unauthenticated users), leading to an unauthenticated SQL Injection

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

## Which versions are affected by CVE-2022-0739?

It affects 1 product.


Products: Reputeinfosystems Bookingpress.

## How do I fix CVE-2022-0739?

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

## Is CVE-2022-0739 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0739 exists.

Public exploit code:

- Proof-of-Concept exploit (SQLI BookingPress  before 1.0.11) (github_poc): https://github.com/destr4ct/CVE-2022-0739
- 🐍 Python Exploit for CVE-2022-0739 (github_poc): https://github.com/BKreisel/CVE-2022-0739
- Simple bash script to automate the exploit of cve 2022 0739 (github_poc): https://github.com/Chris01s/CVE-2022-0739
- Exploit for WP BookingPress (< 1.0.11) based on destr4ct POC. (github_poc): https://github.com/viardant/CVE-2022-0739
- Wordpress BookingPress bookingpress_front_get_category_services SQLi (metasploit)
- CVE-2022-0739 Wordpress BookingPress SQLi (github_poc): https://github.com/hadrian3689/wp_bookingpress_1.0.11

## Other vulnerabilities in Unknown BookingPress – Appointments Booking Calendar Plugin and Online Scheduling Plugin

- [CVE-2024-6467](https://insights.sbomify.com/CVE-2024-6467/): BookingPress Appointment Booking <= 1.1.5 - Authenticated (Subscriber+) Arbitrary File Read to Arbitrary File Creation (high 8.8)
- [CVE-2024-6660](https://insights.sbomify.com/CVE-2024-6660/): Missing authorization in Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress (high 8.8)
- [CVE-2023-50841](https://insights.sbomify.com/CVE-2023-50841/): WordPress BookingPress Plugin <= 1.0.72 is vulnerable to SQL Injection (high 8.5)
- [CVE-2023-51405](https://insights.sbomify.com/CVE-2023-51405/): WordPress BookingPress plugin <= 1.0.74 - Booking Price Manipulation vulnerability (high 8.2)
- [CVE-2025-31910](https://insights.sbomify.com/CVE-2025-31910/): WordPress BookingPress plugin <= 1.1.28 - SQL Injection vulnerability (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0739 and fix it if it is affected.

What it is: CVE-2022-0739 is a critical SQL injection vulnerability in Unknown BookingPress – Appointments Booking Calendar Plugin and Online Scheduling Plugin, published on 21 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0739 exists.

Affected product: Unknown BookingPress – Appointments Booking Calendar Plugin and Online Scheduling 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-2022-0739/ (Markdown: https://insights.sbomify.com/CVE-2022-0739/index.md)
```

## Sources

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

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