# CVE-2026-123668: GetPaid WordPress plugin payment bypass via fractional quantity

Source: https://junglewise.ai/threats/cve-2026-123668-the-getpaid-wordpress-plugin-from-2-8-63-to-2-8-64-does-not  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-11. Updated: 2026-11-11  
License: CC BY 4.0 with a link back

CVE-2026-123668 · Severity: medium · CVSS 5.3 · Published 2026-11-11

GetPaid is a WordPress invoicing plugin used to process payments for goods and services. The plugin fails to validate that item quantities are whole numbers, allowing attackers to manipulate payment forms and mark invoices as paid without actually being charged. An attacker can exploit this to receive products or services without payment.

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

## Quick answers

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

**How severe is CVE-2026-123668?** Medium severity, with a CVSS score of 5.3, published 11 November 2026.

**Which products and versions are affected?** GetPaid 2.8.63 to 2.8.64.

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

**How is CVE-2026-123668 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-123668?** 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.65

## Technical details

The GetPaid plugin does not properly validate that item quantities on payment forms are whole numbers, allowing unauthenticated users to submit fractional quantities that bypass payment requirements. An attacker can craft a request with a fractional quantity value that causes an invoice to be marked as paid without processing the actual charge. The vulnerability affects versions 2.8.63 through 2.8.64 and is fixed in version 2.8.65.

## Affected products

- GetPaid GetPaid 2.8.63 to 2.8.64

## Timeline

- 2026-11-09: disclosed
- 2026-11-11: advisory
- 2026-11-09: patched: Fixed in version 2.8.65; PoC withheld until 2026-11-23

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://wpscan.com/vulnerability/62c1a6ac-0f9f-4402-b72b-8b10ffe6989c/](https://wpscan.com/vulnerability/62c1a6ac-0f9f-4402-b72b-8b10ffe6989c/)

## Related threats

- [GetPaid WordPress plugin improper input validation in payment processing](https://junglewise.ai/threats/cve-2026-119749-the-getpaid-plugin-for-wordpress-before-2-8-63-contains-an)
- [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)