Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesTravelly

Travelly vulnerabilities

Travelly has 9 known vulnerabilities in this database. The most recent published record is dated 20 Nov 2026.

Known vulnerabilities
9
Active installs
1,000+
Latest version
2.3.13
Last updated
9 Nov 2026
Most recent
20 Nov 2026

No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Broken access control
CVE-2026-131760
Medium 5.3Up to 2.3.13No fixed version yet2 d ago
File inclusion
CVE-2026-120839
High 8.8Up to 2.3.8Fixed in a later version (latest 2.3.13)7 Nov 2026
File inclusion
CVE-2026-120841
High 8.8Up to 2.3.8Fixed in a later version (latest 2.3.13)7 Nov 2026
Broken access control
CVE-2026-121794
Medium 6.5Up to 2.3.11Fixed in a later version (latest 2.3.13)6 Nov 2026
Broken access control
CVE-2026-111213
Medium 4.3Up to 2.3.6Fixed in a later version (latest 2.3.13)28 Oct 2026
Cross-site scripting (XSS)
CVE-2026-109590
Medium 6.4Up to 2.3.6Fixed in a later version (latest 2.3.13)28 Oct 2026
Broken access control
CVE-2026-111849
Medium 5.3Up to 2.3.5Fixed in a later version (latest 2.3.13)21 Oct 2026
Broken access control
CVE-2026-62063
Medium 5.4Up to 2.3.1Fixed in a later version (latest 2.3.13)1 Oct 2026
Cross-site request forgery (CSRF)
CVE-2024-0434
Medium 5.3Up to 1.7.1Fixed in a later version (latest 2.3.13)29 May 2024
Read the published descriptions
CVE-2026-131760, 20 Nov 2026
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.13. CVE record
CVE-2026-120839, 7 Nov 2026
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows PHP Local File Inclusion.This issue affects WpTravelly: from n/a through 2.3.8. CVE record
CVE-2026-120841, 7 Nov 2026
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows PHP Local File Inclusion.This issue affects WpTravelly: from n/a through 2.3.8. CVE record
CVE-2026-121794, 6 Nov 2026
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.11 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 view stored WooCommerce payment gateway credentials - including PayPal API username, password, and signature, as well as Stripe test and live secret keys - injected verbatim into the HTML response of the tour edit screen. The credentials are present in the raw HTTP response regardless of the modal's CSS visibility state, making them trivially accessible by viewing page source. CVE record
CVE-2026-111213, 28 Oct 2026
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. CVE record
CVE-2026-109590, 28 Oct 2026
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. CVE record
CVE-2026-111849, 21 Oct 2026
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. CVE record
CVE-2026-62063, 1 Oct 2026
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. CVE record
CVE-2024-0434, 29 May 2024
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. CVE record

What to do if you run Travelly

If you run Travelly, 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 Travelly vulnerabilities

Free. We email you when a new vulnerability is published for Travelly, 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.

Get website support