# CVE-2026-119749: GetPaid WordPress plugin improper input validation in payment processing

Source: https://junglewise.ai/threats/cve-2026-119749-the-getpaid-plugin-for-wordpress-before-2-8-63-contains-an  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-04. Updated: 2026-11-04  
License: CC BY 4.0 with a link back

CVE-2026-119749 · Severity: high · CVSS 7.5 · Published 2026-11-04

GetPaid is a WordPress plugin that handles online payments and invoicing for small businesses. An unauthenticated attacker can bypass payment processing entirely by submitting a negative item quantity on a public payment form, causing an invoice to be marked as paid without any actual payment being collected. This allows an attacker to acquire goods, services, or digital products without paying.

Technologies: [GetPaid](https://junglewise.ai/threats/technologies/getpaid). Vendors: [GetPaid](https://junglewise.ai/threats/vendors/getpaid).

## Quick answers

**Is CVE-2026-119749 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119749 being exploited in the wild.

**How severe is CVE-2026-119749?** High severity, with a CVSS score of 7.5, published 4 November 2026.

**Which products and versions are affected?** GetPaid before 2.8.63.

**Is there a fix for CVE-2026-119749?** Yes: fixed in 2.8.63. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-119749 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-119749?** Check whether you run GetPaid at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.8.63

## Technical details

The vulnerability is an improper input validation flaw in the process_item() function that fails to validate item quantities before calculating line subtotals. An attacker can submit a negative quantity to produce a negative line subtotal, reducing the total invoice amount to zero; the process_free_payment() function then marks the invoice as paid without triggering any payment gateway charge. The vulnerability requires only network access and no authentication or user interaction beyond submitting a form.

## Affected products

- GetPaid GetPaid before 2.8.63

## Timeline

- 2026-11-04: disclosed

## References

- [https://wordpress.org/plugins/invoicing/](https://wordpress.org/plugins/invoicing/)
- [https://www.vulncheck.com/advisories/getpaid-wordpress-plugin-negative-quantity-payment-bypass](https://www.vulncheck.com/advisories/getpaid-wordpress-plugin-negative-quantity-payment-bypass)

## Related threats

- [GetPaid WordPress plugin payment bypass via fractional quantity](https://junglewise.ai/threats/cve-2026-123668-the-getpaid-wordpress-plugin-from-2-8-63-to-2-8-64-does-not)
- [Stiofan GetPaid sensitive data exposure](https://junglewise.ai/threats/cve-2026-49064-stiofan-getpaid-sensitive-data-exposure)
- [WordPress GetPaid Plugin HTML injection in Help Text field](https://junglewise.ai/threats/cve-2021-47948-wordpress-getpaid-plugin-html-injection-in-help-text-field)