Wp Travel EngineWordPress extension · Wptravelengine
CVE-2024-30504
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WP Travel Engine.This issue affects WP Travel Engine: from n/a through 5.7.9.
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 confidenceA SQL Injection vulnerability exists in the WP Travel Engine WordPress plugin (versions up to 5.7.9) due to improper neutralization of special elements in SQL commands. An attacker with administrative privileges could inject malicious SQL queries through unsanitized input parameters, potentially allowing unauthorized data access, modification, or disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Travel EngineWordPress extension
< 5.8.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate WP Travel Engine plugin versionIn WordPress admin dashboard, navigate to Plugins > Installed Plugins > WP Travel Engine and read the version number displayed. Alternatively, check the main plugin file (typically wp-content/plugins/wp-travel-engine/wordpress-travel-engine.php) for the 'Version' header in the plugin comment block.Affected if The reported version is less than 5.8.0 (e.g., 5.7.9, 5.7.8, etc.)
-
Confirm plugin is activeIn WordPress admin, verify that WP Travel Engine is listed as an active (not deactivated) plugin.Affected if The plugin is active and the version is below 5.8.0
-
Identify administrative usersCheck WordPress user administration panel for accounts with Administrator role. The vulnerability requires an attacker with administrative privileges to exploit.Affected if There are administrator-level accounts on the site, which would satisfy the privilege requirement for exploitation.
A site is affected if WP Travel Engine plugin version is below 5.8.0 and the plugin is currently active on the WordPress installation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.8.0
Upgrade WP Travel Engine to the latest version which contains the patched code. If no update is available, implement input validation and use prepared statements for all database queries to prevent SQL injection.
WP Travel Engine 5.8.0
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WP Travel Engine in the plugin list
- Check the current version number to confirm it is below 5.8.0
- Click 'Update Now' if an update is available, or manually upload version 5.8.0 of the plugin
- After updating, verify the plugin version shows 5.8.0
- Test critical booking and travel functionality to ensure the update did not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Travel Engine
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30504 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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