dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12067

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The WP Travel – Ultimate Travel Booking System, Tour Management Engine plugin for WordPress is vulnerable to SQL Injection via the 'booking_itinerary' parameter of the 'wptravel_get_booking_data' function in all versions up to, and including, 10.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 WP Travel plugin for WordPress contains a SQL Injection vulnerability in the 'wptravel_get_booking_data' function. The 'booking_itinerary' parameter is not properly escaped before being used in a SQL query, and the query lacks sufficient preparation (parameterized statements). This allows authenticated attackers with Subscriber-level permissions to inject arbitrary SQL commands and extract sensitive data from the database.

MitigationUpdate the WP Travel plugin to version 10.0.1 or later. Until a patch is available, restrict subscriber-level account creation and monitor for suspicious database query patterns in application logs.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 WP Travel plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Travel' in the list. Alternatively, check the /wp-content/plugins/ directory for the wp-travel folder.
    Affected if WP Travel plugin is not installed on the WordPress site
  2. Check installed WP Travel version
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Travel. The version number is displayed below the plugin name. Compare this version to the affected range (versions prior to 10.0.1).
    Affected if The installed version is prior to 10.0.1
  3. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users and review the list. Check if any users have the 'Subscriber' role assigned. Click on each user to verify their role if needed.
    Affected if At least one user account with Subscriber role exists on the site
  4. Verify the booking_itinerary parameter is processed
    Inspect the WordPress site for any functionality that calls the wptravel_get_booking_data function, particularly endpoints that accept a 'booking_itinerary' parameter in GET or POST requests. Check plugin files (typically in wp-content/plugins/wp-travel/) for calls to this function.
    Affected if The wptravel_get_booking_data function is in use and accepts user input via the booking_itinerary parameter
  5. Review application logs for suspicious SQL patterns
    Check WordPress debug logs (wp-content/debug.log if enabled) and server access/error logs. Search for patterns like UNION SELECT, OR 1=1, or other SQL injection payloads in requests containing 'booking_itinerary' or 'wptravel_get_booking_data'.
    Affected if Log entries show unsanitized SQL-like input being passed to booking parameters

A user is affected if WP Travel plugin version is below 10.0.1, the site has subscriber-level accounts, and the booking_itinerary parameter is accessible or has been exploited.

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 WP Travel plugin to version 10.0.1 or later. Until a patch is available, restrict subscriber-level account creation and monitor for suspicious database query patterns in application logs.

Recommended fix Moderate confidence

version higher than 10.0.0 (check WordPress plugin repository for latest stable release)

  1. Check the current version of the WP Travel plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 10.0.0 or lower, update the plugin to the latest available version

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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