# CVE-2026-13143: WP Travel < 11.8.1 - Unauthenticated Payment Bypass via Forged PayPal IPN

> Unauthenticated attackers can forge PayPal IPN notifications to mark bookings as paid, bypassing payment verification in WP Travel.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-vx7q-rhxw-6x3x

## What is CVE-2026-13143?

CVE-2026-13143 is a medium-severity vulnerability in Unknown WP Travel, published on 30 Jul 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 11.8.1 does not verify PayPal Instant Payment Notifications through the PayPal post-back handshake before marking a booking paid, allowing unauthenticated attackers to forge a notification that flips an arbitrary pending booking to a paid and booked state at an attacker-chosen amount.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-13143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13143 is a medium-severity vulnerability in Unknown WP Travel, published on 30 Jul 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-13143 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-13143/ (Markdown: https://insights.sbomify.com/CVE-2026-13143/index.md)
```

## Sources

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

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