dbcve.org
Wp Travel EngineWordPress extension · Wptravelengine

CVE-2024-37944

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-20
Fix available
A fix is available. Upgrade to 5.9.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in WP Travel Engine allows Stored XSS.This issue affects WP Travel Engine: from n/a through 5.9.1.

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

This is a Stored Cross-Site Scripting (XSS) vulnerability in the WP Travel Engine WordPress plugin. The vulnerability allows an attacker to inject malicious JavaScript code that gets permanently stored in the database and executes when other users view affected pages within the plugin. The root cause is improper input neutralization during web page generation, meaning user-supplied data is not being properly sanitized before being rendered in HTML context.

MitigationUpgrade WP Travel Engine to the latest version available from the vendor, which should contain proper input sanitization and output encoding for all user-supplied data fields within the plugin.

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
Affected:< 5.9.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Engine plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Travel Engine' or 'Wptravelengine Wp Travel Engine' in the list. Note the plugin status (active/inactive).
    Affected if Plugin is installed and active
  2. Determine installed plugin version
    In the Plugins list, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/wp-travel-engine/ or /wp-content/plugins/wptravelengine/ directory for the Version field.
    Affected if Version number is less than 5.9.2
  3. Confirm vulnerable input fields are accessible
    Access the plugin frontend forms where users submit travel booking data (trip booking forms, inquiry forms, or checkout fields). These are the areas where unsanitized input could be stored.
    Affected if Plugin is active AND users can submit data through booking/travel forms provided by the plugin
  4. Inspect page source for unsanitized output
    Submit a test payload containing HTML/script tags (e.g., <script>alert(1)</script>) in plugin booking form fields, complete the submission, then view the resulting page and view its HTML source to see if the payload renders unescaped.
    Affected if HTML/script tags appear literally in the page source (unescaped) indicating the vulnerability is present

You are affected if WP Travel Engine plugin is active, installed version is below 5.9.2, and your site allows users to submit booking or travel data through plugin forms.

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
Upgrade available Upgrade to 5.9.2 or later
Fixed in 5.9.2
Interim mitigation

Upgrade WP Travel Engine to the latest version available from the vendor, which should contain proper input sanitization and output encoding for all user-supplied data fields within the plugin.

Recommended fix High confidence

WP Travel Engine 5.9.2

  1. Create a full backup of your WordPress site before making any changes
  2. Update the WP Travel Engine plugin to version 5.9.2 or later through the WordPress admin dashboard (Plugins > Installed Plugins > WP Travel Engine > Update Now)
  3. Alternatively, upload the updated plugin manually via Plugins > Add New > Upload Plugin
  4. Clear any caching plugins or server-side caches after the update
  5. Verify the plugin version shows 5.9.2 or higher in the plugins list
  6. Test the affected functionality (trip booking, inquiry forms, or wherever the stored XSS was present) to confirm the vulnerability is remediated

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

Fix this in Wp Travel Engine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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