Quick answers
- Is CVE-2026-16737 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16737 being exploited in the wild.
- How severe is CVE-2026-16737?
- Medium severity, with a CVSS score of 5.3, published 12 August 2026.
- Which products and versions are affected?
- WP Travel Engine before 6.8.5.
- Is there a fix for CVE-2026-16737?
- A patch was published on 2026-08-12: Fixed in version 6.8.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16737 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16737?
- Check whether you run WP Travel Engine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an Insecure Direct Object Reference (IDOR) vulnerability in the wte_add_trip_to_cart AJAX action. The vulnerable component fails to perform ownership or authorization checks when a caller-supplied booking_id is processed, allowing unauthenticated users to access and modify arbitrary booking records via sequential ID enumeration. The attack requires obtaining a public nonce from any trip page, then sending a specially crafted JSON payload to wp-admin/admin-ajax.php with the target booking ID. Attackers can disclose booking details (trip info, cost, traveler count, dates) and stored billing information, and can overwrite victim booking records in-place. The vulnerability is specific to the AJAX action; the equivalent REST endpoint properly enforces access controls (returns HTTP 401). Fixed in version 6.8.5.
Affected products
- WP Travel Engine WP Travel Engine before 6.8.5
Timeline
- 2026-08-10: disclosed
- 2026-08-12: patched: Fixed in version 6.8.5