dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-12937

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
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 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
The Tourfic – AI Powered Travel Booking, Hotel Booking & Car Rental WordPress Plugin plugin for WordPress is vulnerable to generic SQL Injection via the 'post_id' parameter in all versions up to, and including, 2.22.7 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. The AJAX handler is registered for unauthenticated users via wp_ajax_nopriv_tf_room_availability, and the required nonce is emitted on the public single-hotel page template, allowing unauthenticated attackers to freely obtain a valid nonce and reach the vulnerable code path.

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 Tourfic WordPress plugin contains a SQL injection vulnerability in its room availability AJAX handler (wp_ajax_nopriv_tf_room_availability). The 'post_id' parameter is not properly escaped and the SQL query lacks prepared statements, allowing unauthenticated attackers to inject arbitrary SQL. The required nonce is publicly exposed on single-hotel pages, making exploitation straightforward.

MitigationUpdate the Tourfic plugin to version 2.22.8 or later. Until patched, consider disabling the affected AJAX endpoint via WordPress hooks or deploying a WAF rule to block malicious post_id values.

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 Tourfic plugin is installed
    Navigate to WordPress admin dashboard > Plugins and verify Tourfic plugin appears in the installed plugins list, or check /wp-content/plugins/ for a tourfic folder
    Affected if Tourfic plugin is installed and active in WordPress
  2. Check installed Tourfic version
    In WordPress admin > Plugins, click on Tourfic to view the version details, or read the Version field from the plugin header in the main PHP file
    Affected if Version is lower than 2.22.8 (the patched release)
  3. Verify the vulnerable AJAX handler exists
    Check if the file includes the tf_room_availability AJAX action by searching for 'add_action("wp_ajax_nopriv_tf_room_availability"' or 'wp_ajax_nopriv_tf_room_availability' in the plugin code
    Affected if The AJAX handler wp_ajax_nopriv_tf_room_availability is registered in the plugin
  4. Confirm nonce is exposed on single-hotel pages
    Visit a published single-hotel page, view the page source, and search for the string 'tf_room_availability' or '_wpnonce' to see if the nonce value is printed in public HTML
    Affected if The nonce required for the AJAX request is visible in the source of publicly accessible hotel pages

The environment is affected if Tourfic plugin version is below 2.22.8 AND the room availability AJAX endpoint is registered and accessible without authentication, allowing the SQL injection to be exploited via the post_id parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Tourfic plugin to version 2.22.8 or later. Until patched, consider disabling the affected AJAX endpoint via WordPress hooks or deploying a WAF rule to block malicious post_id values.

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-2026-12937 — 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-12937 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