Traveler <= 3.1.6 - Missing Authorization in Several AJAX Actions
Strategic Overview
- Status
- Patched in 3.1.7
- Affected Theme
- Travel Booking WordPress Theme
- Affected Version
<= 3.1.6- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-11926
At a glance
CVE-2024-11926 is a medium-severity Missing Authorization vulnerability in the Travel Booking WordPress Theme WordPress theme, affecting versions <= 3.1.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.1.7; sites on affected versions should update now. Disclosed December 2024, reported by Lucio Sá.
Vulnerability Overview
The Travel Booking WordPress Theme theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the '__stPartnerCreateServiceRental', 'st_delete_order_item', '_st_partner_approve_booking', 'save_order_item', and '__userDenyEachInfo' functions in all versions up to, and including, 3.1.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify posts, delete posts and pages, approve arbitrary orders, insert orders with arbitrary prices, and deny user information.
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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Travel Booking WordPress Theme <= 3.1.6 carries this weakness at __stPartnerCreateServiceRental, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Travel Booking WordPress Theme the fix is 3.1.7: builds <= 3.1.6 are affected, anything from 3.1.7 onward is not.
Remediation
Update to version 3.1.7, 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: Travel Booking WordPress Theme 3.1.7 closes this, and updating the theme is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.3CVE-2025-67917: Traveler <= 3.2.6 Missing Authorization
CVE-2025-67917 - 5.3CVE-2025-63028: Traveler <= 3.2.6 Missing Authorization
CVE-2025-63028 - 5.3CVE-2025-59011: Travel Booking WordPress… Unauthenticated Arbitrary
CVE-2025-59011 - 5.3CVE-2025-26733: Traveler <= 3.2.0 Missing Authorization
CVE-2025-26733
Other vulnerabilities in Travel Booking WordPress Theme
- 9.8CVE-2025-26873: Traveler < 3.2.1 PHP Object Injection
CVE-2025-26873 - 9.8CVE-2025-1771: Traveler <= 3.1.8 Local File Inclusion
CVE-2025-1771 - 9.8Travel Booking WordPress Theme < 2.8.4 SQL Injection
- 8.8CVE-2024-12811: Traveler <= 3.1.9 Local File Inclusion
CVE-2024-12811 - 8.3Traveler – Travel Booking WordPress Theme < 2.7.8.6 XSS
- 8.1CVE-2026-25449: Travel Booking WordPress Theme PHP Object Injection
CVE-2026-25449 - 8.1CVE-2025-64373: Traveler < 3.2.6 Local File Inclusion
CVE-2025-64373 - 7.5CVE-2025-52714: Traveler < 3.2.2 SQL Injection
CVE-2025-52714
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C