CVE-2026-1708 json
Appointment Booking Calendar <= 1.6.9.27 - Unauthenticated SQL Injection via 'append_where_sql' Parameter
published 7mo ago modified 4mo ago also EUVD-2026-11117
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to blind SQL Injection in all versions up to, and including, 1.6.9.27. This is due to the `db_where_conditions` method in the `TD_DB_Model` class failing to prevent the `append_where_sql` parameter from being passed through JSON request bodies, while only checking for its presence in the `$_REQUEST` superglobal. This makes it possible for unauthenticated attackers to append arbitrary SQL commands to queries and extract sensitive information from the database via the `append_where_sql` parameter in JSON payloads granted they have obtained a valid `public_token` that is inadvertently exposed during the booking flow.
Is CVE-2026-1708 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- croixhaug Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/71642341-9fe0-44a9-88f3-70167dc6ca62?source=cve
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/trunk/includes/lib/td-util/class-td-db-model.php#L1019
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/tags/1.6.9.21/includes/lib/td-util/class-td-db-model.php#L1019
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/trunk/includes/lib/td-util/class-td-db-model.php#L1025
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/tags/1.6.9.21/includes/lib/td-util/class-td-db-model.php#L1025
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/trunk/includes/class-appointment-model.php#L1340
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/tags/1.6.9.21/includes/class-appointment-model.php#L1340
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/trunk/includes/class-appointment-model.php#L1413
- plugins.trac.wordpress.org /browser/simply-schedule-appointments/tags/1.6.9.21/includes/class-appointment-model.php#L1413
- plugins.trac.wordpress.org /changeset/3475885/simply-schedule-appointments/trunk/includes/lib/td-util/class-td-db-model.php
Sources
- CVE List CVE-2026-1708
- NVD CVE-2026-1708
Fencer Intel 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.