HomeWordPress vulnerabilitiesWP Travel Engine
WP Travel Engine vulnerabilities
WP Travel Engine has 12 known vulnerabilities in this database. The most recent published record is dated 22 Sep 2026.
- Known vulnerabilities
- 12
- Active installs
- 20,000+
- Latest version
- 6.8.9
- Last updated
- 28 Sep 2026
- Most recent
- 22 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| File inclusion CVE-2026-9231 | High 7.5 | Up to 6.8.0 | Fixed in a later version (latest 6.8.9) | 22 Sep 2026 |
| Cross-site request forgery (CSRF) CVE-2026-17087 | High 7.5 | Up to 6.8.4 | Fixed in a later version (latest 6.8.9) | 16 Aug 2026 |
| Broken access control CVE-2026-16737 | Medium 5.3 | Before 6.8.5 | Fixed in 6.8.5 | 12 Aug 2026 |
| Security weakness CVE-2026-12501 | Medium 5.3 | Before 6.8.2 | Fixed in 6.8.2 | 6 Aug 2026 |
| Broken access control CVE-2026-12500 | High 7.5 | Before 6.8.2 | Fixed in 6.8.2 | 30 Jul 2026 |
| Security weakness CVE-2026-10834 | Medium 4.6 | Before 6.8.1 | Fixed in 6.8.1 | 7 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-2437 | Medium 6.4 | Up to 6.7.5 | Fixed in a later version (latest 6.8.9) | 4 Apr 2026 |
| File inclusion CVE-2025-7634 | Critical 9.8 | Up to 6.6.7 | Fixed in a later version (latest 6.8.9) | 9 Oct 2025 |
| Remote code execution CVE-2025-7526 | Critical 9.8 | Up to 6.6.7 | Fixed in a later version (latest 6.8.9) | 9 Oct 2025 |
| Broken access control CVE-2025-5282 | High 7.5 | Before 6.5.2 | Fixed in 6.5.2 | 13 Jun 2025 |
| Broken access control CVE-2024-10606 | Medium 4.3 | Before 6.2.2 | Fixed in 6.2.2 | 23 Nov 2024 |
| Cross-site scripting (XSS) CVE-2021-24680 | Medium 5.4 | Before 5.3.1 | Fixed in 5.3.1 | 3 Jan 2022 |
Read the published descriptions
- CVE-2026-9231, 22 Sep 2026
- 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.8.0 via the wte_get_template function. This makes it possible for authenticated attackers, with contributor-level access and above, 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. CVE record
- CVE-2026-17087, 16 Aug 2026
- The WP Travel Engine - Tour Booking Plugin - Tour Operator Software plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.8.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to view private booking billing details - including the victim customer's first name, last name, email address, street address, city, and phone number - rendered as default values in checkout form fields by binding an arbitrary booking ID to the attacker's session. The only access control on the endpoint is a frontend nonce that is publicly emitted to all visitors via the wteL10n global on trip pages, meaning it provides CSRF protection only and does not restrict unauthenticated access. CVE record
- CVE-2026-16737, 12 Aug 2026
- The WP Travel Engine WordPress plugin before 6.8.5 does not perform authorization or ownership checks when loading a caller-supplied booking identifier in one of its unauthenticated cart actions, allowing unauthenticated attackers to disclose any customer's booking order details and their stored billing information, and to overwrite that customer's booking record with their own data. CVE record
- CVE-2026-12501, 6 Aug 2026
- The WP Travel Engine WordPress plugin before 6.8.2 does not verify that an incoming PayPal payment notification was sent to the site's configured merchant account, nor that the paid amount matches the order total, before marking a booking as paid, allowing unauthenticated attackers to mark bookings as fully paid using a token payment made to an attacker-controlled account. CVE record
- CVE-2026-12500, 30 Jul 2026
- The WP Travel Engine WordPress plugin before 6.8.2 does not perform a capability check on an AJAX action that updates a WP Travel Engine WordPress plugin before 6.8.2 option, allowing unauthenticated users to overwrite a site-wide WP Travel Engine WordPress plugin before 6.8.2 option (the public nonce that gates the action is served to anonymous visitors). CVE record
- CVE-2026-10834, 7 Jul 2026
- The WP Travel Engine WordPress plugin before 6.8.1 does not properly validate the source of a user-supplied profile image path before moving the file, allowing authenticated users with subscriber-level access and above to relocate arbitrary files within the WordPress uploads directory into their own profile-image path. This removes the targeted media from its original location and can break content across the site. CVE record
- CVE-2026-2437, 4 Apr 2026
- The WP Travel Engine - Tour Booking Plugin - Tour Operator Software plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wte_trip_tax' shortcode in all versions up to, and including, 6.7.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-7634, 9 Oct 2025
- 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. CVE record
- CVE-2025-7526, 9 Oct 2025
- The WP Travel Engine - Tour Booking Plugin - Tour Operator Software plugin for WordPress is vulnerable to arbitrary file deletion (via renaming) due to insufficient file path validation in the set_user_profile_image function in all versions up to, and including, 6.6.7. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). CVE record
- CVE-2025-5282, 13 Jun 2025
- The WP Travel Engine - Tour Booking Plugin - Tour Operator Software plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the delete_package() function in all versions up to, and including, 6.5.1. This makes it possible for unauthenticated attackers to delete arbitrary posts. CVE record
- CVE-2024-10606, 23 Nov 2024
- The WP Travel Engine - Tour Booking Plugin - Tour Operator Software plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpte_onboard_save_function_callback() function in all versions up to, and including, 6.2.1. This makes it possible for authenticated attackers, with contributor-level access and above, to modify several settings that could have an impact such as lost revenue and page updates. CVE record
- CVE-2021-24680, 3 Jan 2022
- The WP Travel Engine WordPress plugin before 5.3.1 does not escape the Description field in the Trip Destination/Activities/Trip Type and Pricing Category pages, allowing users with a role as low as editor to perform Stored Cross-Site Scripting attacks, even when the unfiltered_html capability is disallowed CVE record
What to do if you run WP Travel Engine
If you run WP Travel Engine, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Travel Engine vulnerabilities
Free. We email you when a new vulnerability is published for WP Travel Engine, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.