CVE-2026-32358
Blind SQL Injection in wpdevelop Booking Calendar
Publication date: 2026-03-13
Last updated on: 2026-03-13
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wpdevelop | booking_calendar | From 10.0.0 (inc) to 10.14.15 (inc) |
| wpdevelop | booking_calendar | to 10.14.15 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an SQL Injection issue in the wpdevelop Booking Calendar plugin. Specifically, it allows Blind SQL Injection attacks due to improper neutralization of special elements used in SQL commands. This means that an attacker can manipulate SQL queries executed by the plugin to potentially extract or affect data without proper authorization.
How can this vulnerability impact me? :
The vulnerability can have a significant impact as it allows an attacker with high privileges to perform Blind SQL Injection attacks. According to the CVSS score, it can lead to high confidentiality impact and low availability impact, meaning sensitive data could be exposed or compromised, while the system's availability might be slightly affected.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know