| CVE/PSC | Application | Date | Affected versions | Description |
|---|---|---|---|---|
| Actual on: Jun 25, 2026, 01:06:10 | Entries count: 20 | |||
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
May 06, 2025, 19:05:59 |
Min -
Max 6.3.6
|
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel Engine WP Travel Engine wp-travel-engine allows PHP Local File Inclusion.This issue affects WP Travel Engine: from n/a through <= 6.3.5. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jul 14, 2024, 11:07:17 |
Min -
Max 5.9.2
|
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. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 11, 2026, 02:06:16 |
Min -
Max 6.8.0
|
Unauthenticated PHP Object Injection in WP Travel Engine <= 6.7.12 versions. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Nov 24, 2024, 05:11:58 |
Min -
Max 6.2.2
|
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. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Apr 13, 2026, 21:04:06 |
Min -
Max 6.7.6
|
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. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Nov 15, 2024, 02:11:41 |
Min -
Max 5.3.8
|
The Freemius SDK, as used by hundreds of WordPress plugin and theme developers, was vulnerable to Cross-Site Request Forgery and Information disclosure due to missing capability checks and nonce protection on the _get_debug_log, _get_db_option, and the _set_db_option functions in versions up to, and including 2.4.2. Any WordPress plugin or theme running a version of Freemius less than 2.4.3 is vulnerable. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 15, 2025, 11:06:46 |
Min -
Max 6.5.2
|
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. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 15, 2025, 11:06:46 |
Min -
Max 6.5.2
|
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel Engine WP Travel Engine wp-travel-engine allows PHP Local File Inclusion.This issue affects WP Travel Engine: from n/a through <= 6.5.1. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 13, 2026, 19:06:10 |
Min -
Max 5.7.5
|
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in WPVibes WP Mail Log allows DOM-Based XSS. This issue affects WP Mail Log: from n/a through 1.0.2. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Apr 02, 2025, 16:04:52 |
Min -
Max 6.3.6
|
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel Engine WP Travel Engine wp-travel-engine allows PHP Local File Inclusion.This issue affects WP Travel Engine: from n/a through <= 6.3.5. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 12, 2026, 05:06:23 |
Min -
Max 6.7.11
|
Unauthenticated Other Vulnerability Type in WP Travel Engine <= 6.7.10 versions. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Nov 10, 2025, 23:11:25 |
Min -
Max 6.6.8
|
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 includ... | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Nov 10, 2025, 23:11:25 |
Min -
Max 6.6.8
|
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). | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 07, 2024, 03:06:09 |
Min -
Max 5.3.8
|
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 | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 07, 2024, 03:06:09 |
Min -
Max 5.8.1
|
Missing Authorization vulnerability in WP Travel Engine.This issue affects WP Travel Engine: from n/a through 5.8.0. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 07, 2024, 03:06:09 |
Min -
Max 5.8.0
|
Improper 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. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 07, 2024, 03:06:09 |
Min -
Max 5.8.0
|
Improper 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. | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 16, 2026, 06:06:44 |
Min -
Max 5.3.8
|
WP Travel Engine – Tour Booking Plugin – Tour Operator Software [wp-travel-engine] < 5.3.8 WordPress WP Travel Engine plugin <= 5.3.7 - Toggle The Debug Mode via Cross-Site Request Forgery (CSRF) vulnerability Toggle The Debug Mode via Cross-Site Request Forgery (CSRF) vulnerability discovered in WordPress WP Travel Engine plugin (versions <= 5.3.7). | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 16, 2026, 06:06:44 |
Min -
Max 5.3.8
|
WP Travel Engine – Tour Booking Plugin – Tour Operator Software [wp-travel-engine] < 5.3.8 WordPress WP Travel Engine plugin <= 5.3.7 - Sensitive Information Disclosure vulnerability Sensitive Information Disclosure vulnerability discovered in WordPress WP Travel Engine plugin (versions <= 5.3.7). | |
|
WP Travel Engine – Best Travel Booking WordPress Plugin
vulnerable
|
Jun 16, 2026, 06:06:44 |
Min -
Max 5.3.8
|
WP Travel Engine – Tour Booking Plugin – Tour Operator Software [wp-travel-engine] < 5.3.8 Freemius SDK <= 2.4.2 - Missing Authorization Checks The Freemius SDK, as used by hundreds of WordPress plugin and theme developers, was vulnerable to Cross-Site Request Forgery and Information disclosure due to missing capability checks and nonce protection on the _get_debug_log, _get_db_option, and the _set_db_option functions in versions up to, and including 2.4.2. Any WordPress plugin or theme runn... | |