LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1708: Appointment Booking Calendar <= 1.6.9.27 - Unauthenticated SQL Injection via 'append_where_sql' Parameter

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-1708 affects the WordPress “Simply Schedule Appointments” booking plugin. Versions up to and including 1.6.9.27 can allow an unauthenticated attacker to read sensitive database data if they can obtain a public token exposed during the booking flow. This is a confidentiality-focused SQL injection issue, rated high severity.

Executive priority

Treat as a near-term patching priority for public WordPress booking sites. The issue can expose database information without login, but sources do not confirm active exploitation. Prioritize internet-facing sites that collect customer, appointment, or contact data.

Technical view

The issue is blind SQL injection in the plugin’s database filtering logic. The db_where_conditions method blocks append_where_sql from $_REQUEST, but the CVE states JSON request bodies can still pass it through. With a valid public_token, an unauthenticated attacker may append SQL to backend queries and extract database information.

Likely exposure

Internet-facing WordPress sites using Appointment Booking Calendar / Simply Schedule Appointments at version 1.6.9.27 or earlier are the primary exposure. Risk is higher where booking flows are public and expose usable public_token values.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation is described as unauthenticated but dependent on obtaining a valid public_token during the booking flow. The impact cited is sensitive information disclosure through blind SQL injection.

Researcher notes

Do not assume a fixed version from the provided data. The bundle references a WordPress Trac changeset and vulnerable code locations, but the safe operational recommendation is to follow vendor/plugin release guidance. Public exploitation status is not established by KEV or the supplied sources.

Mitigation direction

  • Identify sites using the Simply Schedule Appointments WordPress plugin.
  • Check whether installed versions are 1.6.9.27 or earlier.
  • Review vendor and WordPress plugin guidance for the fixed release.
  • Apply the vendor-provided update when available and tested.
  • Restrict or disable public booking flows if immediate updating is not possible.
  • Monitor web and database logs for unusual booking API activity.

Validation and detection

  • Inventory WordPress plugins across managed sites.
  • Confirm the installed Simply Schedule Appointments version.
  • Review whether public booking pages expose public_token values.
  • Compare installed code against WordPress changeset 3475885.
  • Check security tooling for CVE-2026-1708 coverage.
  • Verify remediation after updating by confirming the vulnerable version is no longer present.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1708 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-1708Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
croixhaugAppointment Booking Calendar — Simply Schedule Appointments Booking Plugin0unaffected
Weakness

CWE details

CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs