# CVE-2026-90987: Easy PayPal & Stripe Buy Now Button 1.8 - 2.0.5 - Unauthenticated Payment Amount Manipulation via Client-Supplied Price

> Unauthenticated attackers can manipulate payment amounts by supplying arbitrary prices, bypassing intended pricing logic in the Easy PayPal & Stripe Buy Now Button plugin.

- **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:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-x5h3-rq2w-f7cx

## What is CVE-2026-90987?

CVE-2026-90987 is a medium-severity vulnerability in Unknown Easy PayPal & Stripe Buy Now Button, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Easy PayPal & Stripe Buy Now Button WordPress plugin before 2.0.6 does not derive the payment amount on the server, taking it from a client-supplied field, so an unauthenticated attacker sets an arbitrary lower price for a purchase.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2026-90987 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90987 is a medium-severity vulnerability in Unknown Easy PayPal & Stripe Buy Now Button, published on 2 Oct 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-90987 in the wild and no public exploit code.

Affected product: Unknown Easy PayPal & Stripe Buy Now Button. 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-90987/ (Markdown: https://insights.sbomify.com/CVE-2026-90987/index.md)
```

## Sources

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

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