Skip to content
Noroxi

Travelly – Tour & Travel Booking Manager for WooCommerce

tour-booking-manager · plugin

Known security vulnerabilities for Travelly – Tour & Travel Booking Manager for WooCommerce. Find out in seconds which version runs on your site with WP Lens.

10 known vulnerabilities

5 exploitable without logging in · latest Oct 1, 2026

Listed on wordpress.org · latest 2.3.5 · last updated Oct 6, 2026 · 1K+ installs

wordpress.org status checked on Oct 10, 2026

Vulnerabilities

  • CVE-2025-30892login required≤ 1.8.7

    WordPress WpTravelly Plugin <= 1.8.7 - PHP Object Injection vulnerability

    High 8.8

  • CVE-2025-30891login required≤ 1.8.7

    WordPress WpTravelly Plugin <= 1.8.7 - Local File Inclusion vulnerability

    High 8.8

  • CVE-2026-27089unauthenticated≤ 2.1.7

    WordPress WpTravelly plugin <= 2.1.7 - Bypass Vulnerability vulnerability

    High 7.5

  • CVE-2024-43212unauthenticated≤ 1.7.7

    WordPress WpTravelly plugin <= 1.7.7 - Broken Access Control vulnerability

    High 7.5

  • CVE-2026-27331login required≤ 2.1.5

    WordPress WpTravelly plugin <= 2.1.5 - Broken Access Control vulnerability

    Medium 6.3

  • CVE-2026-62063login required≤ 2.3.1

    WordPress WpTravelly plugin <= 2.3.1 - Broken Access Control vulnerability

    Medium 5.4

  • CVE-2025-22737unauthenticated≤ 1.8.5

    WordPress WpTravelly Plugin <= 1.8.5 - Broken Access Control vulnerability

    Medium 5.3

  • CVE-2024-0434unauthenticated≤ 1.7.1

    WordPress Tour & Travel Booking Plugin for WooCommerce – WpTravelly <= 1.7.1 - Missing Authorization via ttbm_new_place_save

    Medium 5.3

  • CVE-2024-32450unauthenticated · needs a click≤ 1.6.0

    WordPress WpTravelly plugin <= 1.6.0 - Cross Site Request Forgery (CSRF) vulnerability

    Medium 4.3

  • CVE-2026-39565login required≤ 2.1.7

    WordPress WpTravelly plugin <= 2.1.7 - Broken Access Control vulnerability

    Medium 4.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory