# CVE-2026-12501: WP Travel Engine < 6.8.2 - Unauthenticated Payment Bypass via Missing PayPal IPN Receiver and Amount Verification

> Unauthenticated attackers can bypass payment verification in WP Travel Engine to mark bookings as paid without valid transactions.

- **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:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-v4gx-m8c5-cqwv

## What is CVE-2026-12501?

CVE-2026-12501 is a medium-severity vulnerability in Unknown WP Travel Engine, published on 6 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.2 does not verify that an incoming PayPal payment notification was sent to the site's configured merchant account, nor that the paid amount matches the order total, before marking a booking as paid, allowing unauthenticated attackers to mark bookings as fully paid using a token payment made to an attacker-controlled account.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-12501 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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