CVE-2026-16737

Travel Engine <= 6.8.4 - Insecure Direct Object Reference to Unauthenticated Booking Details Disclosure and Modification

2026-08-10 00:00
Usama Arshad

Strategic Overview

Status
Patched in 6.8.5
Affected Plugin
WP Travel Engine – Tour Booking Plugin – Tour Operator Software
Affected Version
<= 6.8.4
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-16737
View all WP Travel Engine – Tour Booking Plugin – Tour Operator Software vulnerabilities

At a glance

CVE-2026-16737 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 6.8.4. 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 6.8.5; sites on affected versions should update now. Disclosed August 2026, reported by Usama Arshad.

Vulnerability Overview

The Travel Engine plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 6.8.4. This is due to missing ownership check on the caller-supplied `booking_id` parameter in the AddToCart AJAX handler, allowing any unauthenticated user to reference arbitrary booking posts. This makes it possible for unauthenticated attackers to view or modify booking details belonging to other users by supplying an arbitrary booking ID to the wte_add_trip_to_cart AJAX 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 privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP Travel Engine <= 6.8.4 takes no account at all. 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 Engine the fix is 6.8.5: builds <= 6.8.4 are affected, anything from 6.8.5 onward is not.

Remediation

Update to version 6.8.5, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Travel Engine 6.8.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-16737https://www.wordfence.com/threat-intel/vulnerabilities/id/4077dd33-bd3c-4369-b9ed-b6b6b017248dhttps://nvd.nist.gov/vuln/detail/CVE-2026-16737

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C