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