WordPress Tour & Travel Booking Plugin for WooCommerce – WpTravelly <= 1.7.1 - Missing Authorization via ttbm_new_place_save
Strategic Overview
- Status
- Patched in 1.7.2
- Affected Plugin
- Travelly – Tour & Travel Booking Manager for WooCommerce
- Affected Version
<= 1.7.1- CVSS
- 5.3Medium
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE-2024-0434
At a glance
CVE-2024-0434 is a medium-severity Improper Access Control vulnerability in the Travelly WordPress plugin, affecting versions <= 1.7.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7.2; sites on affected versions should update now. Disclosed May 2024, reported by Francesco Carlucci.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-284: Improper Access Control
Travelly <= 1.7.1 carries this weakness at ttbm_new_place_save, and reaching it takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Travelly the fix is 1.7.2: builds <= 1.7.1 are affected, anything from 1.7.2 onward is not.
Remediation
Update to version 1.7.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Travelly 1.7.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Travelly – Tour & Travel Booking Manager for WooCommerce
- 8.8CVE-2025-30892: WpTravelly <= 1.8.7 PHP Object Injection
CVE-2025-30892 - 8.8CVE-2025-30891: WpTravelly <= 1.8.7 Local File Inclusion
CVE-2025-30891 - 5.3CVE-2026-27089: Travelly Missing Authorization
CVE-2026-27089 - 5.3CVE-2025-22737: WpTravelly <= 1.8.5 Missing Authorization
CVE-2025-22737 - 5.3CVE-2024-43212: WpTravelly <= 1.7.7 Missing Authorization
CVE-2024-43212 - 4.3CVE-2026-27331: Travelly Missing Authorization
CVE-2026-27331 - 4.3CVE-2026-39565: WpTravelly <= 2.1.7 Missing Authorization
CVE-2026-39565 - 4.3CVE-2024-32450: WpTravelly <= 1.6.0 Cross-Site Request Forgery
CVE-2024-32450
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C