dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39493

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unauthenticated SQL Injection in Simply Schedule Appointments <= 1.6.9.27 versions.

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

Unauthenticated SQL injection vulnerability in the Simply Schedule Appointments WordPress plugin versions up to 1.6.9.27 allows remote attackers to execute arbitrary SQL commands through unsanitized user input without requiring any authentication credentials.

MitigationUpgrade Simply Schedule Appointments to version 1.6.9.28 or later to apply the security patch that properly sanitizes SQL queries.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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. Verify Simply Schedule Appointments plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/simply-schedule-appointments directory exists on the server
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Simply Schedule Appointments to view the version number, or check the main plugin file for the 'Version' header comment
    Affected if The version is 1.6.9.27 or earlier
  3. Confirm the plugin is active
    In WordPress admin, check if Simply Schedule Appointments shows as 'Active' in the Plugins list, or query the wp_options table for option_name = 'ssa_settings' with a non-empty option_value
    Affected if The plugin is active and processing requests
  4. Verify the vulnerable SQL query handling is reachable
    The vulnerability exists in unsanitized user input handling within the plugin. Check if the plugin's AJAX endpoints or REST API routes under simply-schedule-appointments are exposed (no authentication required for exploitation). Inspect plugin source code for direct $_GET, $_POST, or $_REQUEST usage in SQL queries.
    Affected if Unauthenticated access to plugin AJAX/REST endpoints is allowed and plugin processes SQL queries with user input

A WordPress site is affected if Simply Schedule Appointments plugin version 1.6.9.27 or earlier is installed and active, processing unauthenticated requests that could contain malicious SQL input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Simply Schedule Appointments to version 1.6.9.28 or later to apply the security patch that properly sanitizes SQL queries.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39493 — 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-39493 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