Free tool
Is my WordPress plugin safe?
Type a plugin or theme and the version you run, and we’ll show every known vulnerability that affects it, from the 390,007 records in our vulnerability database. The version is listed under Plugins in your WordPress dashboard.
Not this one?Booking ManagerWpTravellyTaxi Booking Manager for WooCommerceWpBookinglyDesignThemes Booking ManagerMultipurpose Ticket Booking Manager
Plugin · tour-booking-manager
WpTravelly
13 known vulnerabilities on record. Add your version above to see which ones affect you.
Oct 28, 2026Travelly – Tour & Travel Booking Manager for WooCommerce: Authorization bypassCVE-2026-111213 · affects up to 2.3.6 · reported by WordfenceMedium 4.3
The Travelly – Tour & Travel Booking Manager for WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.3.6 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to duplicate arbitrary posts — including private, draft, and pending posts authored by Administrators and Editors — into drafts they own, thereby exposing the original post's content, excerpt, title, taxonomies, and metadata. A Contributor can harvest a valid nonce from the Duplicate row-action on their own posts list and reuse it against any victim post ID, since the nonce action is the static string 'TTBM_Admin.php' and is not bound to any specific post.
Oct 28, 2026Tour Booking Manager: Stored Cross-Site ScriptingCVE-2026-109590 · affects up to 2.3.6 · reported by WordfenceMedium 6.4
The Tour Booking Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'width', 'height' and 'zoom' shortcode attributes of the [ttbm-hotel-map] shortcode in versions up to, and including, 2.3.6 This is due to insufficient input sanitization and output escaping on user supplied attributes in the ttbm_hotel_map_shortcode() function, which concatenates the raw attribute values into double-quoted HTML attributes of an <iframe> tag. 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.
Oct 21, 2026WpTravelly: Missing AuthorizationCVE-2026-111849 · affects up to 2.3.5 · reported by PatchstackMedium 5.3
Missing Authorization vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WpTravelly: from n/a through 2.3.5.
Oct 1, 2026WpTravelly: Missing AuthorizationCVE-2026-62063 · affects up to 2.3.1 · reported by PatchstackMedium 5.4
Missing Authorization vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WpTravelly: from n/a through 2.3.1.
Jun 15, 2026Unauthenticated Bypass Vulnerability in WpTravelly <= 2.1.7 versions.CVE-2026-27089 · affects up to 2.1.7 · reported by PatchstackHigh 7.5
Unauthenticated Bypass Vulnerability in WpTravelly <= 2.1.7 versions.
May 26, 2026WpTravelly: Missing AuthorizationCVE-2026-27331 · affects up to 2.1.5 · reported by PatchstackMedium 6.3
Missing Authorization vulnerability in Magepeople inc. WpTravelly allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WpTravelly: from n/a through 2.1.5.
Apr 8, 2026WpTravelly: Missing AuthorizationCVE-2026-39565 · affects up to 2.1.7 · reported by PatchstackMedium 4.3
Missing Authorization vulnerability in magepeopleteam WpTravelly tour-booking-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WpTravelly: from n/a through <= 2.1.7.
Apr 1, 2025WpTravelly: Deserialization of Untrusted DataCVE-2025-30892 · affects up to 1.8.7 · reported by PatchstackHigh 8.8
Deserialization of Untrusted Data vulnerability in magepeopleteam WpTravelly tour-booking-manager allows Object Injection.This issue affects WpTravelly: from n/a through <= 1.8.7.
Mar 27, 2025WpTravelly: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')CVE-2025-30891 · affects up to 1.8.7 · reported by PatchstackHigh 8.8
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in magepeopleteam WpTravelly tour-booking-manager allows PHP Local File Inclusion.This issue affects WpTravelly: from n/a through <= 1.8.7.
Jan 15, 2025WpTravelly: Missing AuthorizationCVE-2025-22737 · affects up to 1.8.5 · reported by PatchstackMedium 5.3
Missing Authorization vulnerability in magepeopleteam WpTravelly tour-booking-manager allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WpTravelly: from n/a through <= 1.8.5.
Nov 1, 2024WpTravelly: Missing AuthorizationCVE-2024-43212 · affects up to 1.7.7 · reported by PatchstackHigh 7.5
Missing Authorization vulnerability in MagePeople Team WpTravelly allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WpTravelly: from n/a through 1.7.7.
May 29, 2024WordPress Tour & Travel Booking Plugin for WooCommerce – WpTravelly: Unauthorized modification of dataCVE-2024-0434 · affects up to 1.7.1 · reported by WordfenceMedium 5.3
The WordPress Tour & Travel Booking Plugin for WooCommerce – WpTravelly plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ttbm_new_place_save' function in all versions up to, and including, 1.7.1. This makes it possible for unauthenticated attackers to create and publish new place posts. This function is also vulnerable to CSRF.
NVD recordplugins.trac.wordpress.orgplugins.trac.wordpress.org
Apr 15, 2024WpTravelly: Cross-Site Request Forgery (CSRF)CVE-2024-32450 · affects up to 1.6.0 · reported by PatchstackMedium 4.3
Cross-Site Request Forgery (CSRF) vulnerability in MagePeople Team WpTravelly.This issue affects WpTravelly: from n/a through 1.6.0.
Versions are matched against the affected ranges published with each record. A plugin can ship a fix under its own numbering, so if something looks off, check the linked record. Want the whole site checked at once? Run the free website check.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.