CVE-2026-119749

Payment forms, Buy now buttons, and Invoicing System | GetPaid <= 2.8.62 - Unauthenticated Payment Processing Bypass

2026-11-04 00:00
Idan Malihi

Strategic Overview

Status
Patched in 2.8.63
Affected Version
<= 2.8.62
CVSS
5.3Medium
Weakness type
CWE-1284 · Improper Validation of Specified Quantity in Input
CVE
CVE-2026-119749
View all Payment forms, Buy now buttons, and Invoicing System | GetPaid vulnerabilities

At a glance

CVE-2026-119749 is a medium-severity Improper Validation of Specified Quantity in Input vulnerability in the Payment forms, Buy now buttons, and Invoicing System WordPress plugin, affecting versions <= 2.8.62. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.63; sites on affected versions should update now. Disclosed November 2026, reported by Idan Malihi.

Vulnerability Overview

The Payment forms, Buy now buttons, and Invoicing System | GetPaid plugin for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 2.8.62. This is due to missing validation on the user-supplied quantity value in the process_item() function, allowing negative numbers to produce a negative line subtotal. This makes it possible for unauthenticated attackers to manipulate invoice totals to zero by submitting a negative item quantity on a public payment form, causing the invoice to be marked as paid without any actual payment being collected. A payment form with an item that allows customers to set quantities must be publicly accessible.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-1284: Improper Validation of Specified Quantity in Input

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

Remediation

Update to version 2.8.63, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Payment forms, Buy now buttons, and Invoicing System 2.8.63 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C