dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12166

HIGH · 7.5 CVSS v3.1 Published 2026-01-14
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 via the `order` and `append_where_sql` parameters in all versions up to, and including, 1.6.9.9 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.

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 escape the `order` and `append_where_sql` parameters and lacks prepared statements in the underlying SQL queries. This allows unauthenticated attackers to inject arbitrary SQL code via these parameters, enabling blind SQL injection to extract sensitive database contents.

MitigationUpdate the plugin to version 1.7.0 or later which contains the fix. If immediate updating is not feasible, consider deploying a WAF rule to block SQL injection payloads or temporarily disable the plugin.

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 is installed
    Check if the Simply Schedule Appointments plugin is present in your WordPress installation. In the WordPress admin, go to Plugins > Installed Plugins and look for 'Simply Schedule Appointments'. Alternatively, check if the directory wp-content/plugins/simply-schedule-appointments exists.
    Affected if The plugin is installed and present in the environment
  2. Check installed plugin version
    Locate the plugin version number. In WordPress admin, view the plugin details on the Plugins page. Or inspect the main plugin file (simply-schedule-appointments.php) and look for the 'Version' header in the plugin comment block. Compare this version number against the fixed version 1.7.0.
    Affected if The installed version is lower than 1.7.0 (for example, 1.6.9, 1.6.8, etc.)
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Simply Schedule Appointments shows as 'Active'. Or run: wp plugin status simply-schedule-appointments
    Affected if The plugin is active and running on the site
  4. Check for suspicious SQL injection traffic
    Review web server access logs and any available WAF/security plugin logs for requests containing the parameters 'order' or 'append_where_sql' with unusual SQL characters such as quotes, UNION, SELECT, SLEEP, or boolean operators. grep your access logs for these parameter names.
    Affected if Exploitation attempts are found in logs, or if the plugin version is below 1.7.0 with these parameters accessible to unauthenticated users

If Simply Schedule Appointments is installed, active, and the version is below 1.7.0, the environment is affected by this unauthenticated SQL injection vulnerability.

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.7.0 or later which contains the fix. If immediate updating is not feasible, consider deploying a WAF rule to block SQL injection payloads or temporarily disable the plugin.

Recommended fix Moderate confidence

Latest version available at wordpress.org (version after 1.6.9.9)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Simply Schedule Appointments' (Appointment Booking Calendar)
  4. Check if the current version is 1.6.9.9 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/simply-schedule-appointments/ and upload manually

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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