Description
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.
References10
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/…
- plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/…
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 1% percentile: 53 · as of 11 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.