# CVE-2026-13146: WP Travel < 12.0.2 - Unauthenticated Booking Payment State Tampering via IDOR

> Unauthenticated attackers can tamper with booking payment states and attach files by exploiting missing ownership verification in WP Travel.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-7w4q-cq3r-2frw

## What is CVE-2026-13146?

CVE-2026-13146 is a low-severity missing authorization vulnerability in Unknown WP Travel, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Travel  WordPress plugin before 12.0.2 does not properly verify that the requester owns the booking targeted by its bank-deposit slip submission, allowing an unauthenticated attacker who knows the target customer's email address to change that customer's booking payment state and attach a file to it.

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

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


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

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

## Is CVE-2026-13146 being exploited?

There is no known exploitation of CVE-2026-13146 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13146 is a low-severity missing authorization vulnerability in Unknown WP Travel, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13146 in the wild and no public exploit code.

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-13146/ (Markdown: https://insights.sbomify.com/CVE-2026-13146/index.md)
```

## Sources

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

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