dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1708

HIGH · 7.5 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Simply Schedule Appointments WordPress plugin fails to sanitize the `append_where_sql` parameter in JSON request bodies. The code only checks for this parameter in the `$_REQUEST` superglobal, allowing attackers to bypass this check by sending JSON payloads with the malicious parameter, enabling unauthenticated blind SQL injection via the exposed `public_token`.

MitigationUpdate the plugin to version 1.6.9.28 or later which includes proper sanitization of JSON body parameters for SQL injection prevention.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Simply Schedule Appointments plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Simply Schedule Appointments', or check the /wp-content/plugins/ directory for the simply-schedule-appointments folder
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin > Plugins, find Simply Schedule Appointments and view the version number under the plugin name, or read the main plugin file header in /wp-content/plugins/simply-schedule-appointments/
    Affected if The version is lower than 1.6.9.28
  3. Verify the public_token is exposed
    Make an unauthenticated GET request to the plugin's public-facing AJAX endpoint or REST API route (commonly /wp-json/ssa/v1/ or ?action=ssa_ajax) and examine if a public_token parameter is returned in the response
    Affected if A valid public_token is discoverable and returned by the plugin API
  4. Test for the JSON-based SQL injection vector
    Send a POST request with a JSON body containing the append_where_sql parameter to the plugin's AJAX or REST API endpoint, using the exposed public_token for authentication, for example: POST /wp-admin/admin-ajax.php with Content-Type: application/json and body: {"public_token":"[TOKEN]","append_where_sql":"1=1"}
    Affected if The plugin accepts JSON body parameters with append_where_sql and processes them without sanitization, indicating the vulnerable code path is reachable

The environment is affected if Simply Schedule Appointments version is below 1.6.9.28, the plugin's public_token is exposed or guessable, and the REST API/AJAX endpoint accepts JSON payloads with the append_where_sql parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.6.9.28 or later which includes proper sanitization of JSON body parameters for SQL injection prevention.

Recommended fix High confidence

1.6.9.28 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin'
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1708 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1708 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data