# CVE-2026-119749: GetPaid WordPress Plugin < 2.8.63 Negative Quantity Payment Bypass


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-mxp8-89wv-42r2

## What is CVE-2026-119749?

CVE-2026-119749 is a high-severity vulnerability in AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid, published on 4 Nov 2026. 

### Official description

The GetPaid plugin for WordPress before 2.8.63 contains an improper input validation vulnerability that allows unauthenticated attackers to bypass payment processing by submitting a negative item quantity on a public payment form. Attackers can exploit the unchecked quantity value in process_item() to produce a negative line subtotal that reduces the invoice total to zero, causing process_free_payment() to mark the invoice as paid without any actual gateway charge.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

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

## Is CVE-2026-119749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119749 is a high-severity vulnerability in AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119749 in the wild and no public exploit code.

Affected product: AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid. 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-119749/ (Markdown: https://insights.sbomify.com/CVE-2026-119749/index.md)
```

## Sources

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

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