WordPress plugin · Updated daily · Source: Wordfence Intelligence

WP Travel Engine vulnerabilities: affected versions and fixes

WP Travel Engine has 20,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

WP Travel Engine at a glance

  • 23 publicly disclosed vulnerabilities, 11 of them rated High or Critical. The most recent was disclosed on Sep 21, 2026.
  • Ranked #1334 by popularity on WordPress.org (20,000+ active installs).
  • The latest version is 6.9.0 (released Nov 16, 2026). The most recent security fix shipped in 6.8.1.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your WP Travel Engine version

Enter the WP Travel Engine version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “WP Travel Engine”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WP Travel Engine”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (6.9.0). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known WP Travel Engine vulnerabilities

  • WP Travel Engine <= 6.8.0 - Authenticated (Contributor+) Local File Inclusion via 'template' Shortcode Attribute

    Arbitrary file read or deletion · CVE-2026-9231

    Affected versions: ≤ 6.8.0

    Fixed in: 6.8.1

    Severity: High 7.5 · Disclosed Sep 21, 2026

  • WP Travel Engine <= 6.8.4 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'booking_id' Parameter

    Missing authorization · CVE-2026-17087

    Affected versions: ≤ 6.8.4

    Fixed in: 6.8.5

    Severity: High 7.5 · Disclosed Aug 15, 2026

  • Travel Engine <= 6.8.4 - Insecure Direct Object Reference to Unauthenticated Booking Details Disclosure and Modification

    Missing authorization · CVE-2026-16737

    Affected versions: ≤ 6.8.4

    Fixed in: 6.8.5

    Severity: Medium 5.3 · Disclosed Aug 10, 2026

  • WP Travel Engine – Tour Booking Plugin – Tour Operator Software < 6.8.2 - Missing Authorization to Unauthenticated Settings Update

    Missing authorization · CVE-2026-12500

    Affected versions: < 6.8.2

    Fixed in: 6.8.2

    Severity: Medium 5.3 · Disclosed Aug 5, 2026

  • Travel Engine <= 6.8.1 - Unauthenticated Payment Bypass

    Missing authorization · CVE-2026-12501

    Affected versions: ≤ 6.8.1

    Fixed in: 6.8.2

    Severity: Medium 5.3 · Disclosed Jul 13, 2026

  • Travel Engine <= 6.8.0 - Authenticated (Subscriber+) Arbitrary Media File Move

    Other weakness · CVE-2026-10834

    Affected versions: ≤ 6.8.0

    Fixed in: 6.8.1

    Severity: Medium 4.3 · Disclosed Jun 16, 2026

  • WP Travel Engine – Tour Booking Plugin – Tour Operator Software <= 6.7.10 - Missing Authorization

    Missing authorization · CVE-2026-49078

    Affected versions: ≤ 6.7.10

    Fixed in: 6.7.11

    Severity: Medium 5.3 · Disclosed Jun 5, 2026

  • WP Travel Engine – Tour Booking Plugin – Tour Operator Software <= 6.7.12 - Unauthenticated PHP Object Injection

    PHP object injection · CVE-2026-49770

    Affected versions: ≤ 6.7.12

    Fixed in: 6.8.0

    Severity: High 8.1 · Disclosed Jun 4, 2026

  • WP Travel Engine - Travel and Tour Booking Plugin <= 6.7.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via wte_trip_tax Shortcode

    Cross-site scripting (XSS) · CVE-2026-2437

    Affected versions: ≤ 6.7.5

    Fixed in: 6.7.6

    Severity: Medium 6.4 · Disclosed Apr 3, 2026

  • WP Travel Engine – Tour Booking Plugin – Tour Operator Software <= 6.6.7 - Authenticated (Subscriber+) Arbitrary File Deletion via File Renaming

    Arbitrary file read or deletion · CVE-2025-7526

    Affected versions: ≤ 6.6.7

    Fixed in: 6.6.8

    Severity: Critical 9.8 · Disclosed Oct 8, 2025

  • WP Travel Engine – Tour Booking Plugin – Tour Operator Software <= 6.6.7 - Unauthenticated Local File Inclusion

    Arbitrary file read or deletion · CVE-2025-7634

    Affected versions: ≤ 6.6.7

    Fixed in: 6.6.8

    Severity: Critical 9.8 · Disclosed Oct 8, 2025

  • WP Travel Engine <= 6.5.1 - Missing Authorization to Unauthenticated Arbitrary Post Deletion

    Missing authorization · CVE-2025-5282

    Affected versions: ≤ 6.5.1

    Fixed in: 6.5.2

    Severity: High 7.5 · Disclosed Jun 12, 2025

  • WP Travel Engine <= 6.5.1 - Authenticated (Contributor+) Local File Inclusion

    Arbitrary file read or deletion · CVE-2025-49308

    Affected versions: ≤ 6.5.1

    Fixed in: 6.5.2

    Severity: High 8.8 · Disclosed Jun 5, 2025

  • WP Travel Engine <= 6.3.5 - Unauthenticated Local File Inclusion

    Arbitrary file read or deletion · CVE-2025-30870

    Affected versions: ≤ 6.3.5

    Fixed in: 6.3.6

    Severity: Critical 9.8 · Disclosed Mar 27, 2025

  • WP Travel Engine <= 6.3.5 - Authenticated (Contributor+) Local File Inclusion

    Arbitrary file read or deletion · CVE-2025-30871

    Affected versions: ≤ 6.3.5

    Fixed in: 6.3.6

    Severity: High 8.8 · Disclosed Mar 27, 2025

  • WP Travel Engine <= 6.2.1 - Missing Authorization to Authenticated (Contributor+) Plugin Settings Update

    Missing authorization · CVE-2024-10606

    Affected versions: ≤ 6.2.1

    Fixed in: 6.2.2

    Severity: Medium 4.3 · Disclosed Nov 22, 2024

  • WP Travel Engine <= 5.9.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-37944

    Affected versions: ≤ 5.9.1

    Fixed in: 5.9.2

    Severity: Medium 6.4 · Disclosed Jul 10, 2024

  • WP Travel Engine <= 5.8.0 - Unauthenticated Price Manipulation

    Other weakness · CVE-2024-32798

    Affected versions: ≤ 5.8.0

    Fixed in: 5.8.1

    Severity: Medium 5.3 · Disclosed Apr 22, 2024

  • WP Travel Engine <= 5.7.9 - Unauthenticated SQL Injection

    SQL injection · CVE-2024-30502

    Affected versions: ≤ 5.7.9

    Fixed in: 5.8.0

    Severity: Critical 10 · Disclosed Mar 28, 2024

  • WP Travel Engine <= 5.7.9 - Authenticated (Administrator+) SQL Injection

    SQL injection · CVE-2024-30504

    Affected versions: ≤ 5.7.9

    Fixed in: 5.8.0

    Severity: Critical 9.1 · Disclosed Mar 28, 2024

  • Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_get

    Cross-site scripting (XSS) · CVE-2023-33999

    Affected versions: ≤ 5.7.4

    Fixed in: 5.7.5

    Severity: Medium 6.1 · Disclosed Jul 18, 2023

  • Freemius SDK <= 2.4.2 - Missing Authorization Checks

    Missing authorization · CVE-2022-4974

    Affected versions: < 5.3.8

    Fixed in: 5.3.8

    Severity: Medium 6.3 · Disclosed Mar 4, 2022

  • WP Travel Engine <= 5.3.0 - Editor+ Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24680

    Affected versions: ≤ 5.3.0

    Fixed in: 5.3.1

    Severity: Medium 5.5 · Disclosed Dec 1, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 21, 2026.

Most common weaknesses in WP Travel Engine

Missing authorization

8 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Arbitrary file read or deletion

6 issues

An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.

Cross-site scripting (XSS)

4 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Frequently asked questions

Is WP Travel Engine safe to use?

WP Travel Engine is a well-known plugin with 20,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (6.9.0) and turn on automatic updates.

How do I find which version of WP Travel Engine my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesWP Travel Engine on WordPress.org