dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3496

HIGH · 7.5 CVSS v3.1 Published 2026-03-11
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 JetBooking plugin for WordPress is vulnerable to SQL Injection via the 'check_in_date' parameter in all versions up to, and including, 4.0.3. This is 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 JetBooking WordPress plugin versions up to 4.0.3 contain a SQL Injection vulnerability in the 'check_in_date' parameter. The plugin fails to properly escape user-supplied input and does not use prepared statements, allowing unauthenticated attackers to inject arbitrary SQL queries and potentially extract sensitive data from the database.

MitigationUpdate to the latest version of JetBooking when available. Until a patch is released, consider deploying a WAF rule to filter or block malicious SQL characters in the check_in_date 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. Confirm JetBooking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for JetBooking in the list, or check the /wp-content/plugins/ directory for the jetbooking folder
    Affected if JetBooking plugin is present on the WordPress site
  2. Check installed JetBooking version
    In WordPress admin, go to Plugins > Installed Plugins, find JetBooking, and view the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/jetbooking/includes or similar main file
    Affected if Version is 4.0.3 or lower (any version up to and including 4.0.3)
  3. Verify booking functionality is accessible
    Identify if the booking calendar or check-in date form is exposed on the site, typically on a front-end booking page, accommodation search, or availability check widget. Visit pages where JetBooking booking forms are rendered
    Affected if The check_in_date parameter is accepted via HTTP request (GET or POST) on any public booking-related page
  4. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify JetBooking shows as 'Active' rather than 'Inactive' or 'Network Active'
    Affected if Plugin status is Active and the booking feature is publicly accessible

If JetBooking version 4.0.3 or lower is installed and active, and the booking check-in date feature is exposed on the site, the environment is affected by this 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 to the latest version of JetBooking when available. Until a patch is released, consider deploying a WAF rule to filter or block malicious SQL characters in the check_in_date parameter.

Recommended fix Moderate confidence

JetBooking version 4.0.4 or latest stable release

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the JetBooking plugin and check the current version
  4. If the installed version is 4.0.3 or lower, click Update Now to upgrade to the latest available version
  5. Alternatively, download the latest version from the WordPress plugin repository or from crocoblock.com
  6. After updating, verify the plugin is running version 4.0.4 or higher
Caveat Review plugin changelog for any booking behavior changes that may affect existing reservations

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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