WP Travel Engine <= 6.8.4 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'booking_id' Parameter
Strategic Overview
- Status
- Patched in 6.8.5
- Affected Version
<= 6.8.4- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-17087
At a glance
CVE-2026-17087 is a high-severity Missing Authorization vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 6.8.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). 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 Supakiad S. (m3ez).
Vulnerability Overview
The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.8.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to view private booking billing details — including the victim customer's first name, last name, email address, street address, city, and phone number — rendered as default values in checkout form fields by binding an arbitrary booking ID to the attacker's session. The only access control on the endpoint is a frontend nonce that is publicly emitted to all visitors via the wteL10n global on trip pages, meaning it provides CSRF protection only and does not restrict unauthenticated access.
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. A successful exploit has high impact on confidentiality.
CWE-862: Missing Authorization
Reaching this weakness in WP Travel Engine <= 6.8.4 takes no account at all. 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 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
Related records
Same weakness class
- 7.5CVE-2025-5282: WP Travel… Unauthenticated Arbitrary Post Deletion
CVE-2025-5282 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 5.3CVE-2026-12500: WP Travel Engine Unauthenticated Settings Update
CVE-2026-12500 - 5.3CVE-2026-49078: WP Travel Engine Missing Authorization
CVE-2026-49078
Other vulnerabilities in WP Travel Engine – Tour Booking Plugin – Tour Operator Software
- 10.0CVE-2024-30502: WP Travel Engine <= 5.7.9 SQL Injection
CVE-2024-30502 - 9.8CVE-2025-7634: WP Travel Engine LFI
CVE-2025-7634 - 9.8CVE-2025-7526: WP Travel Engine Arbitrary File Deletion
CVE-2025-7526 - 9.8CVE-2025-30870: WP Travel Engine <= 6.3.5 Local File Inclusion
CVE-2025-30870 - 9.1CVE-2024-30504: WP Travel Engine <= 5.7.9 SQL Injection
CVE-2024-30504 - 8.8CVE-2025-49308: WP Travel Engine <= 6.5.1 Local File Inclusion
CVE-2025-49308 - 8.8CVE-2025-30871: WP Travel Engine <= 6.3.5 Local File Inclusion
CVE-2025-30871 - 8.1CVE-2026-49770: WP Travel Engine PHP Object Injection
CVE-2026-49770
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C