CVE-2026-7797
Time-Based Blind SQL Injection in Appointment Booking Calendar WordPress Plugin
Publication date: 2026-05-28
Last updated on: 2026-05-28
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| simply_schedule_appointments | appointment_booking_calendar | to 1.6.11.8 (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?
The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin for WordPress has a time-based blind SQL Injection vulnerability in the 'append_where_sql' parameter in all versions up to 1.6.11.8. This occurs because the plugin does not properly escape user-supplied input and does not sufficiently prepare the existing SQL query. As a result, unauthenticated attackers can append additional SQL queries to existing ones, potentially extracting sensitive information from the database.
The vulnerability is exploitable via the /appointments/bulk REST endpoint, which is accessible without authentication due to a permission check that accepts a public nonce embedded in the booking widget's frontend JavaScript. Attackers can exploit this by sending a PUT request with an application/x-www-form-urlencoded body, bypassing PHP superglobal population and blocklist checks.
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated attackers to extract sensitive information from your website's database by injecting SQL queries. Since the attack does not require authentication, it poses a significant risk of data exposure. The extracted data could include personal information, booking details, or other confidential data stored in the database.
The CVSS score of 7.5 indicates a high severity impact, meaning the vulnerability can lead to serious confidentiality breaches without requiring user interaction or privileges.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated attackers to perform time-based blind SQL Injection to extract sensitive information from the database.
Exposure of sensitive information due to this vulnerability could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access.
Therefore, exploitation of this vulnerability may result in violations of these standards by compromising the confidentiality of protected data.