# CVE-2026-16734: Stripe Payment Forms by WP Full Pay < 8.5.2 - Unauthenticated Payment Intent Amount Manipulation

> Unauthenticated attackers can manipulate payment intent amounts via unprotected AJAX actions, leading to unauthorized price changes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 6 Aug 2026
- **Also known as:** GHSA-8673-2q96-2vmf

## What is CVE-2026-16734?

CVE-2026-16734 is a high-severity vulnerability in Unknown Stripe Payment Forms by WP Full Pay, 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 Stripe Payment Forms by WP Full Pay  WordPress plugin before 8.5.2 does not verify that the caller owns the Stripe payment intent referenced by two unauthenticated payment-form AJAX actions, allowing an unauthenticated visitor — using a nonce that is embedded in every public page containing a payment form — to change the amount of a payment intent that the Stripe Payment Forms by WP Full Pay  WordPress plugin before 8.5.2 then updates server-side through the Stripe API with the store's secret key. An ownership check added in 8.5.0 was applied to only one payment-intent handler, leaving the pricing-recalculation and payment-intent-update actions unprotected against amount manipulation.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-16734 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16734 is a high-severity vulnerability in Unknown Stripe Payment Forms by WP Full Pay, 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-16734 exists.

Affected product: Unknown Stripe Payment Forms by WP Full Pay. 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-16734/ (Markdown: https://insights.sbomify.com/CVE-2026-16734/index.md)
```

## Sources

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

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