dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1250

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
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 Court Reservation – Manage Your Court Bookings Online plugin for WordPress is vulnerable to generic SQL Injection via the ‘id’ parameter in all versions up to, and including, 1.10.11 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 Court Reservation WordPress plugin fails to properly sanitize and escape the 'id' parameter before using it in SQL queries, combined with use of unparameterized SQL queries. This allows unauthenticated attackers to inject arbitrary SQL commands via the vulnerable 'id' parameter, potentially extracting sensitive data from the database.

MitigationUpdate the plugin to the latest version immediately; if no update is available, disable the plugin or implement a WAF rule to block SQL injection attempts targeting the 'id' parameter.

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 Court Reservation plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'court-reservation' or search the WordPress database in the wp_options table for option_name='active_plugins'
    Affected if The plugin files exist in the plugins directory or the plugin is listed in active_plugins
  2. Identify installed plugin version
    Inspect the main plugin PHP file (usually court-reservation.php) for the Version header comment, or check the plugin's readme.txt file
    Affected if The version number cannot be determined or falls within an affected version range (compare to any official advisory)
  3. Confirm plugin is active
    Query the wp_options table for option_name='active_plugins' and check if the serialized array contains court-reservation
    Affected if The plugin appears in the active_plugins array
  4. Test for vulnerable parameter exposure
    Send an HTTP GET request to typical WordPress endpoints using the 'id' parameter (e.g., ?id=1 or ?action=edit&id=1), then use boolean-based SQL injection testing (e.g., ?id=1 AND 1=1 vs ?id=1 AND 1=2)
    Affected if The application responds differently to true vs false SQL conditions, indicating SQL injection is possible
  5. Check for unparameterized SQL usage
    Review plugin source code for direct usage of $wpdb->query(), $wpdb->get_results(), or similar without $wpdb->prepare() using the 'id' parameter
    Affected if The code uses the 'id' parameter in raw SQL queries without parameterization

The environment is affected if the Court Reservation plugin is installed, active, and uses unparameterized SQL queries with the 'id' parameter accessible via HTTP requests.

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 the latest version immediately; if no update is available, disable the plugin or implement a WAF rule to block SQL injection attempts targeting the 'id' parameter.

Recommended fix Moderate confidence

Version 1.10.12 or later of Court Reservation – Manage Your Court Bookings Online plugin

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Court Reservation – Manage Your Court Bookings Online' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/court-reservation and upload it
  5. After updating, verify the plugin version is 1.10.12 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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