# CVE-2026-16990: Payment Button for PayPal <= 1.2.3.44 - Unauthenticated Payment Price Manipulation

> Unauthenticated attackers can manipulate payment amounts in the PayPal WordPress plugin, allowing them to create orders for arbitrary lower prices.

- **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-4h7v-8qrm-x2jj

## What is CVE-2026-16990?

CVE-2026-16990 is a medium-severity vulnerability in Unknown Payment Button for PayPal, 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 Payment Button for PayPal WordPress plugin through 1.2.3.44 does not enforce the merchant-configured price server-side and trusts a client-supplied payment amount, allowing unauthenticated attackers to create a real PayPal order against the merchant for an arbitrary lower amount.

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


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

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

## Is CVE-2026-16990 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16990 is a medium-severity vulnerability in Unknown Payment Button for PayPal, 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-16990 in the wild and no public exploit code.

Affected product: Unknown Payment Button for PayPal. 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-16990/ (Markdown: https://insights.sbomify.com/CVE-2026-16990/index.md)
```

## Sources

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

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