Skip to main content
← Vulnerabilities

GetPaid WordPress Plugin < 2.8.63 Negative Quantity Payment Bypass

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.63
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.8.63.

29Pcve.now Index 29 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Data gap: Advisories don't say whether default setups are affected
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

CVE-2026-119749 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Payment forms, Buy now buttons, and Invoicing System | GetPaid; fixed in 2.8.63.

Published
Last modified
Published
Not listed in CISA KEV
29/100 · provisional
Unclear
Fix
Fixed in 2.8.63
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

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.

What to do

  • Upgrade to a fixed version: 2.8.63.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid

    fixed in 2.8.63

Evidence 2

  1. Patch
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-119749

Is CVE-2026-119749 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Submitting a negative item quantity on a public payment form can make an invoice be marked as paid without any actual payment going through the gateway. The flaw lets an unauthenticated visitor skip payment processing.Source: vulncheck.com

Which versions are affected by CVE-2026-119749?

Payment forms, Buy now buttons, and Invoicing System | GetPaid: before 2.8.63.Source: cve.now feed data

Am I affected, and how do I check?

Versions of the GetPaid plugin for WordPress before 2.8.63 are listed as affected. The setup involves a public payment form that accepts an item quantity; to check, look at the GetPaid plugin version under the WordPress Plugins screen and see whether any payment or buy-now form on the site accepts quantities.Source: vulncheck.com

How do I fix CVE-2026-119749?

Update the GetPaid plugin to version 2.8.63 or later, which is the listed fixed version. No vendor-provided fix details beyond that version are included in the checked facts.Source: vulncheck.com