dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-7634

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 6.6.7 via the mode parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

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 Engine WordPress plugin suffers from an unauthenticated Local File Inclusion vulnerability via the 'mode' parameter in versions up to 6.6.7. Attackers can include and execute arbitrary .php files present on the server, potentially achieving remote code execution by leveraging existing writable PHP files or other file inclusion primitives.

MitigationUpdate the WP Travel Engine plugin to version 6.6.8 or later immediately. Until patched, consider disabling the plugin or deploying WAF rules to block directory traversal patterns in URL parameters.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WP Travel Engine plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the 'wp-travel-engine' folder, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin folder exists in the plugins directory or the plugin is listed in active_plugins in the database
  2. Determine the installed version of WP Travel Engine
    Check the plugin main file header (wp-content/plugins/wp-travel-engine/plugin.php) for the 'Version' comment, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'wp_travel_engine_version';
    Affected if The version number returned is 6.6.7 or lower (any version up to and including 6.6.7)
  3. Verify the plugin is active
    Check if the plugin is enabled in WordPress admin under Plugins > Installed Plugins, or verify it is not commented out in the active_plugins array in wp_options
    Affected if The plugin is currently active and running on the site
  4. Identify if the vulnerable parameter handler exists
    Inspect the plugin files for code handling the 'mode' parameter, typically in ajax handlers or admin-post.php calls. Look for include/require statements using $_REQUEST['mode'] or $_POST['mode'] without proper sanitization.
    Affected if The plugin code contains a 'mode' parameter handler that performs file inclusion without sanitizing the input
  5. Test if the endpoint is externally accessible
    Identify the URL endpoint processing the 'mode' parameter (commonly admin-ajax.php or a custom AJAX handler) and verify it accepts unauthenticated requests. Attempt a benign inclusion test if you have authorization.
    Affected if The endpoint processing the 'mode' parameter is accessible to unauthenticated users without requiring authentication tokens

You are affected if WP Travel Engine plugin version 6.6.7 or earlier is installed and active on your WordPress site, with the vulnerable 'mode' parameter handler accessible.

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 Engine plugin to version 6.6.8 or later immediately. Until patched, consider disabling the plugin or deploying WAF rules to block directory traversal patterns in URL parameters.

Recommended fix High confidence

Version 6.6.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WP Travel Engine' plugin
  4. Check the current installed version - if it is 6.6.7 or earlier, an update is required
  5. Click 'Update Now' or 'Update' to install the latest version
  6. After updating, verify the new version number reflects 6.6.8 or higher
  7. If automatic updates are not enabled, manually download the latest version from wordpress.org/plugins/wp-travel-engine/ and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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