# CVE-2026-16737: WP Travel Engine < 6.8.5 - Unauthenticated Booking Details Disclosure and Modification via wte_add_trip_to_cart

> Unauthenticated attackers can view and modify any customer's booking details and billing information due to missing authorization checks in the cart action.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-4rf8-mj4r-9mgw

## What is CVE-2026-16737?

CVE-2026-16737 is a medium-severity missing authorization vulnerability in Unknown WP Travel Engine, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Travel Engine  WordPress plugin before 6.8.5 does not perform authorization or ownership checks when loading a caller-supplied booking identifier in one of its unauthenticated cart actions, allowing unauthenticated attackers to disclose any customer's booking order details and their stored billing information, and to overwrite that customer's booking record with their own data.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-16737?


## How do I fix CVE-2026-16737?

No fix has been published for CVE-2026-16737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16737 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16737 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16737 and fix it if it is affected.

What it is: CVE-2026-16737 is a medium-severity missing authorization vulnerability in Unknown WP Travel Engine, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16737 exists.

Affected product: Unknown WP Travel Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16737/ (Markdown: https://insights.sbomify.com/CVE-2026-16737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16737
- OSV: https://osv.dev/vulnerability/CVE-2026-16737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16737/
Summaries are generated and may contain mistakes; the official description above is the record.