dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3658

HIGH · 7.5 CVSS v3.1 Published 2026-03-19
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 SQL Injection via the 'fields' parameter in all versions up to, and including, 1.6.10.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database, including usernames, email addresses, and password hashes.

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 properly sanitize the 'fields' parameter before using it in an SQL query. An unauthenticated attacker can inject arbitrary SQL commands by manipulating this parameter, potentially extracting sensitive database contents including WordPress user credentials.

MitigationUpdate to version 1.6.11.0 or later which contains proper escaping and prepared statement usage for the affected SQL query.

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. Verify plugin installation status
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Simply Schedule Appointments' in the list. Note whether it is installed and active.
    Affected if The plugin is installed and active on the WordPress site.
  2. Identify installed plugin version
    Click on the plugin name in the Plugins page to view details, or check the plugin header in simply-schedule-appointments.php for the 'Version' constant. Compare the version number to the affected range (versions before 1.6.11.0).
    Affected if The installed version is lower than 1.6.11.0.
  3. Confirm unauthenticated access to affected endpoint
    Test if the WordPress site allows unauthenticated requests to the endpoint that processes the 'fields' parameter. This is typically an AJAX or REST API endpoint used by the plugin's booking/appointment forms accessible to visitors.
    Affected if The plugin exposes an endpoint that accepts the 'fields' parameter without authentication.
  4. Inspect SQL query usage of fields parameter
    Examine the plugin source code, specifically looking for SQL queries that incorporate the 'fields' parameter directly without prepared statements or proper escaping. Search for 'fields' in database query functions within the plugin files.
    Affected if Code exists that uses the 'fields' parameter directly in SQL queries without parameterization.

A user is affected if Simply Schedule Appointments is installed with a version lower than 1.6.11.0 and the plugin exposes an endpoint that processes the 'fields' parameter in SQL queries without prepared statements.

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 to version 1.6.11.0 or later which contains proper escaping and prepared statement usage for the affected SQL query.

Recommended fix Moderate confidence

Version 1.6.10.1 or latest stable release

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'Appointment Booking Calendar — Simply Schedule Appointments' plugin
  3. 3. Check the current installed version in the plugin details
  4. 4. If the installed version is 1.6.10.0 or lower, navigate to Plugins > Add New > Upload Plugin or check for an update via the WordPress updates
  5. 5. Upgrade to version 1.6.10.1 or the latest available version that includes the security fix
  6. 6. After upgrade, verify the plugin is functioning correctly and consider reviewing activity logs for any signs of exploitation prior to patching

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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