dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-56064

HIGH · 8.5 CVSS v3.1 Published 2026-06-26
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 8 weeks old

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
Subscriber SQL Injection in Tourfic <= 2.22.5 versions.

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

A SQL injection vulnerability exists in the Tourfic WordPress plugin (a hotel/tour booking system) affecting versions up to and including 2.22.5. The flaw allows authenticated users with subscriber-level privileges to execute arbitrary SQL queries through unsanitized input, potentially exposing sensitive database information or manipulating data.

MitigationUpdate Tourfic plugin to a version newer than 2.22.5. If immediate update is not possible, consider restricting subscriber role capabilities or deploying a WAF rule to detect SQL injection patterns.

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 Tourfic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Tourfic' or check the filesystem under wp-content/plugins/tourfic/ and read the main plugin file header for the Version field
    Affected if Tourfic plugin is present in the WordPress installation
  2. Check installed Tourfic version
    Read the plugin version from the plugin header in wp-content/plugins/tourfic/tourfic.php or from the WordPress plugins admin page
    Affected if The reported version is 2.22.5 or any earlier version (versions up to and including 2.22.5 are affected)
  3. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users and review user roles. Subscriber role is the lowest privilege level that can exploit this vulnerability
    Affected if Any user account with subscriber role (or higher) exists in the WordPress site
  4. Identify accessible plugin endpoints
    Review Tourfic plugin files (especially any AJAX handlers or form processing files) for parameters that accept user input and construct SQL queries without prepared statements
    Affected if The plugin processes user input through SQL queries without proper sanitization or parameterization

A user is affected if the Tourfic plugin version is 2.22.5 or earlier AND at least one subscriber-level user account exists in WordPress, allowing authenticated SQL injection.

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 Tourfic plugin to a version newer than 2.22.5. If immediate update is not possible, consider restricting subscriber role capabilities or deploying a WAF rule to detect SQL injection patterns.

Recommended fix Moderate confidence

Tourfic version 2.22.6 or later (upgrade to the latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Tourfic plugin in the list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Dashboard > Updates and update the Tourfic plugin
  6. Verify the update was successful by checking the plugin version is newer than 2.22.5
Caveat Review the plugin's changelog before upgrading to check for any breaking changes or required configuration adjustments

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-56064 — 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-56064 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