# CVE-2026-17008: Quick PayPal Payments <= 5.7.50 - Unauthenticated Payment Bypass via PayPal IPN

> Attackers can bypass payment verification in Quick PayPal Payments by sending forged IPN messages, marking unpaid orders as paid.

- **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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-wpmj-p56j-6mq2

## What is CVE-2026-17008?

CVE-2026-17008 is a medium-severity vulnerability in Unknown Quick Paypal Payments, 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 Quick Paypal Payments WordPress plugin through 5.7.50 does not verify the paid amount, receiver, or payment status in its PayPal IPN handler and marks an order paid on an order-token match alone, so a buyer who pays an arbitrary small amount can have a full-price order marked paid.

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


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

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

## Is CVE-2026-17008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17008 is a medium-severity vulnerability in Unknown Quick Paypal Payments, published on 12 Aug 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-17008 in the wild and no public exploit code.

Affected product: Unknown Quick Paypal Payments. 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-17008/ (Markdown: https://insights.sbomify.com/CVE-2026-17008/index.md)
```

## Sources

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

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