dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-27263

HIGH · 8.5 CVSS v3.1 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Creativeitem Doctor Appointment Booking doctor-appointment-booking allows SQL Injection.This issue affects Doctor Appointment Booking: from n/a through <= 1.0.0.

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

SQL Injection vulnerability in Creativeitem Doctor Appointment Booking plugin allows attackers to inject malicious SQL commands through unsanitized user inputs in the booking functionality. The plugin fails to properly neutralize special elements in SQL queries, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate to a patched version of the plugin that implements proper input sanitization and uses parameterized queries (prepared statements) instead of string concatenation for SQL commands. If no patch exists, temporarily disable the plugin until a fix is available.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the plugin is installed
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'doctor' or 'doctor-appointment-booking' or search the plugins list in the WordPress admin dashboard
    Affected if The Creativeitem Doctor Appointment Booking plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number displayed under the plugin name, or check the main plugin PHP file for a version constant
    Affected if The installed version matches any vulnerable version range (compare against known affected versions if available)
  3. Confirm booking functionality is enabled
    Navigate to the plugin settings in WordPress admin and verify the booking functionality is active, or check if any booking-related shortcode or page is published
    Affected if The booking feature is enabled and publicly accessible
  4. Test for SQL injection exposure
    Using a web proxy or browser developer tools, submit a booking form with a single quote (') in text fields such as name or email, then check if the response contains a SQL error message
    Affected if The application returns SQL syntax errors or behaves unexpectedly with special characters in input fields
  5. Review server logs for SQL errors
    Check your web server error logs (Apache/Nginx error.log) and PHP error logs for SQL syntax errors occurring around booking form submissions
    Affected if SQL error messages appear in logs related to booking functionality

A user is affected if they have the vulnerable version of the Creativeitem Doctor Appointment Booking plugin installed with booking functionality enabled and accessible, demonstrated by SQL errors when submitting special characters in booking form fields.

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 a patched version of the plugin that implements proper input sanitization and uses parameterized queries (prepared statements) instead of string concatenation for SQL commands. If no patch exists, temporarily disable the plugin until a fix is available.

Recommended fix Moderate confidence

Latest version > 1.0.0 (specific fixed release version not specified in provided description)

  1. 1. Check the current version of the Doctor Appointment Booking plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. If a newer version than 1.0.0 is available, update the plugin to the latest version
  4. 4. Verify the update completed successfully
  5. 5. Test the appointment booking functionality to ensure the plugin still works correctly after the update
  6. 6. Review patchstack.com or the WordPress plugin repository for the specific fixed release version for CVE-2025-27263
Caveat Minor or major version upgrade may introduce changes; review plugin changelog before updating on production sites

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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