Is Travelly safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.3.10). As of 2026-11-04. 13 issues are on record for older versions; version 2.3.8 or newer fixes all of them that state a fix. Keep Travelly on the latest version (2.3.10) and remove it if you do not use it.

Which versions of Travelly are vulnerable?

Known issues on record (newest first): Missing authorization check (2.3.6 and older, fixed in 2.3.8); Stored cross-site scripting (XSS) (2.3.6 and older, fixed in 2.3.8); Missing authorization check (2.3.5 and older, fixed in 2.3.6); Missing authorization check (2.3.1 and older, fixed in 2.3.2); Security issue (2.1.7 and older, fixed in 2.1.8); Missing authorization check (2.1.5 and older, fixed in 2.1.6). The full list with sources is on this page.

What is the latest version of Travelly?

2.3.10, according to wordpress.org (last updated 2026-11-03). It has 1,000+ active installs.

What should I do if my Travelly is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update tour-booking-manager). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · tour-booking-manager · data as of 2026-11-04

Is Travelly safe? Known vulnerabilities and latest version

Latest version: 2.3.10
Last updated: 2026-11-03
Active installs: 1,000+
Known issues on record: 13
Unpatched in latest: 0
Tested up to WP: 7.0.8 · PHP 7.0+

Travelly is a WordPress tour and travel booking plugin for WooCommerce. Sell tours, manage hotel bookings, and accept payments online. — by magepeopleteam

What to do

Update to the latest version (2.3.10). Anything older than 2.3.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get tour-booking-manager --field=version shows what you run; wp plugin update tour-booking-manager updates it.

Check your version

Known vulnerabilities

13 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2026-111213 · published 2026-10-28

Missing authorization check in Travelly (2.3.6 and older)

Affected: 2.3.6 and older
Fixed in: 2.3.8 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-111213 Wordfence advisory Code change (fix)github.com Plugin source

medium 6.4 CVE-2026-109590 · published 2026-10-28

Stored cross-site scripting (XSS) in Travelly (2.3.6 and older)

Affected: 2.3.6 and older
Fixed in: 2.3.8 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-109590 Wordfence advisory Code change (fix)github.com Plugin source

medium 5.3 CVE-2026-111849 · published 2026-10-21

Missing authorization check in Travelly (2.3.5 and older)

Affected: 2.3.5 and older
Fixed in: 2.3.6
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2026-111849 Patchstack advisory

medium 5.4 CVE-2026-62063 · published 2026-10-01

Missing authorization check in Travelly (2.3.1 and older)

Affected: 2.3.1 and older
Fixed in: 2.3.2
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

NVD CVE-2026-62063 Patchstack advisory

high 7.5 CVE-2026-27089 · published 2026-06-15

Security issue in Travelly (2.1.7 and older)

Affected: 2.1.7 and older
Fixed in: 2.1.8
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Bypass Vulnerability in WpTravelly <= 2.1.7 versions.

NVD CVE-2026-27089 Patchstack advisory

medium 6.3 CVE-2026-27331 · published 2026-05-26

Missing authorization check in Travelly (2.1.5 and older)

Affected: 2.1.5 and older
Fixed in: 2.1.6
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2026-27331 Patchstack advisory

medium 4.3 CVE-2026-39565 · published 2026-04-08

Missing authorization check in Travelly (2.1.7 and older)

Affected: 2.1.7 and older
Fixed in: 2.1.8
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2026-39565 Patchstack advisory

high 8.8 CVE-2025-30892 · published 2025-04-01

PHP object injection in Travelly (1.8.7 and older)

Affected: 1.8.7 and older
Fixed in: 1.8.8
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2025-30892 Patchstack advisory

high 8.8 CVE-2025-30891 · published 2025-03-27

File inclusion in Travelly (1.8.7 and older)

Affected: 1.8.7 and older
Fixed in: 1.8.8
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2025-30891 Patchstack advisory

medium 5.3 CVE-2025-22737 · published 2025-01-15

Missing authorization check in Travelly (1.8.5 and older)

Affected: 1.8.5 and older
Fixed in: 1.8.6
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2025-22737 Patchstack advisory

high 7.5 CVE-2024-43212 · published 2024-11-01

Missing authorization check in Travelly (1.7.7 and older)

Affected: 1.7.7 and older
Fixed in: 1.7.8
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2024-43212 Patchstack advisory

medium 5.3 CVE-2024-0434 · published 2024-05-29

Cross-site request forgery (CSRF) in Travelly (1.7.1 and older)

Affected: 1.7.1 and older
Fixed in: 2.0.6 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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 CVE-2024-0434 Wordfence advisory Code change (fix)Plugin source

medium 4.3 CVE-2024-32450 · published 2024-04-15

Cross-site request forgery (CSRF) in Travelly (1.6.0 and older)

Affected: 1.6.0 and older
Fixed in: 1.6.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in MagePeople Team WpTravelly.This issue affects WpTravelly: from n/a through 1.6.0.

NVD CVE-2024-32450 Patchstack advisory

Recent activity

2026-11-03 — latest release on wordpress.org (2.3.10).
2026-10-28 — Missing authorization check disclosed (CVE-2026-111213), fixed in 2.3.8.
2026-10-28 — Stored cross-site scripting (XSS) disclosed (CVE-2026-109590), fixed in 2.3.8.
2026-10-21 — Missing authorization check disclosed (CVE-2026-111849), fixed in 2.3.6.

Free. We check the CVE feeds every day and email you only when a new issue for Travelly (tour-booking-manager) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (7) · Cross-site request forgery (CSRF) (2) · Cross-site scripting (XSS) (1) · PHP object injection (1) · File inclusion (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/tour-booking-manager (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/tour-booking-manager"><img src="https://laskyr.com/plugins/tour-booking-manager/badge.svg" alt="Travelly vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Travelly safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.3.10)

What to do

Check your version

Known vulnerabilities

Missing authorization check in Travelly (2.3.6 and older)

Stored cross-site scripting (XSS) in Travelly (2.3.6 and older)

Missing authorization check in Travelly (2.3.5 and older)

Missing authorization check in Travelly (2.3.1 and older)

Security issue in Travelly (2.1.7 and older)

Missing authorization check in Travelly (2.1.5 and older)

Missing authorization check in Travelly (2.1.7 and older)

PHP object injection in Travelly (1.8.7 and older)

File inclusion in Travelly (1.8.7 and older)

Missing authorization check in Travelly (1.8.5 and older)

Missing authorization check in Travelly (1.7.7 and older)

Cross-site request forgery (CSRF) in Travelly (1.7.1 and older)

Cross-site request forgery (CSRF) in Travelly (1.6.0 and older)

Recent activity

Get an email when Travelly has a new vulnerability

Browse vulnerabilities

Where this data comes from