WP Travel – Ultimate Travel Booking System, Tour Management Engine < 11.8.1 - Authenticated (Subscriber+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 11.8.1
- Affected Version
< 11.8.1- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-13145
At a glance
CVE-2026-13145 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Travel WordPress plugin, affecting versions < 11.8.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 11.8.1; sites on affected versions should update now. Disclosed July 2026, reported by Revanth Hari Narayana Matte.
Vulnerability Overview
The WP Travel – Ultimate Travel Booking System, Tour Management Engine plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to 11.8.1 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.
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 interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in WP Travel < 11.8.1 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP Travel the fix is 11.8.1: builds < 11.8.1 are affected, anything from 11.8.1 onward is not.
Remediation
Update to version 11.8.1, or a newer patched version
How WordSec helps
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: WP Travel 11.8.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Travel – Ultimate Travel Booking System, Tour Management Engine
- 7.5CVE-2023-47224: WP Travel <= 7.7.0 Missing Authorization
CVE-2023-47224 - 6.5CVE-2026-45218: WP Travel SQL Injection
CVE-2026-45218 - 6.5CVE-2025-22691: WP Travel <= 10.1.3 SQL Injection
CVE-2025-22691 - 6.5CVE-2024-12067: WP Travel SQL Injection
CVE-2024-12067 - 6.5CVE-2024-53813: WP Travel <= 9.6.0 Missing Authorization
CVE-2024-53813 - 5.3CVE-2026-11868: Travel <= 11.7.0 Missing Authorization
CVE-2026-11868 - 5.3CVE-2026-24568: Travel <= 11.1.0 Missing Authorization
CVE-2026-24568 - 4.4CVE-2024-44039: WP Travel <= 9.3.1 Stored Cross-Site Scripting
CVE-2024-44039
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C