CVE-2022-0739 in the critical feed json
BookingPress < 1.0.11 - Unauthenticated SQL Injection
published 2022-03-21 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-15806
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 37.4%
- EPSS 37.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Metasploit
Summary
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
Patch / fix
Timeline
- First public exploit (Metasploit auxiliary/gather/wp_bookingpress_category_services_sqli)
- Published
Exploit prediction
37.42% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/gather/wp_bookingpress_category_services_sqli Wordpress BookingPress bookingpress_front_get_category_services SQLi metasploit auxiliary, normal rank, 2022-02-28
- wpscan.com https://wpscan.com/vulnerability/388cd42d-b61a-42a4-8604-99b812db2357 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Unknown BookingPress – Appointments Booking Calendar Plugin and Online Scheduling Plugin
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2684789
patch, third-party-advisory
-
wpscan.com
/vulnerability/388cd42d-b61a-42a4-8604-99b812db2357
exploit, third-party-advisory
Sources
- CVE List CVE-2022-0739
- NVD CVE-2022-0739
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.