# CVE-2026-13145: WP Travel < 11.8.1 - Subscriber+ Booking PII Disclosure via IDOR

> Logged-in users can access other customers' booking details and billing addresses by manipulating booking identifiers in the WP Travel plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-29jr-2w77-7q4c

## What is CVE-2026-13145?

CVE-2026-13145 is a medium-severity missing authorization vulnerability in Unknown WP Travel, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Travel  WordPress plugin before 11.8.1 does not verify that the booking requested on its customer account dashboard belongs to the current user, allowing any logged-in user to read another customer's booking details, including billing address information, by supplying an arbitrary booking identifier.

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

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


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

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

## Is CVE-2026-13145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13145 is a medium-severity missing authorization vulnerability in Unknown WP Travel, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13145 exists.

Affected product: Unknown WP Travel. 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-13145/ (Markdown: https://insights.sbomify.com/CVE-2026-13145/index.md)
```

## Sources

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

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