Auth bypass in Ayecode Ltd Payment Forms, Buy Now Buttons, And Invoicing System | Getpaid
CVE-2026-119748
The GetPaid plugin for WordPress before 2.8.63 contains an authorization bypass vulnerability that allows unauthenticated attackers to access and manipulate another user's invoice by supplying its ID through the maybe_use_invoice parameter in process_invoice(), bypassing the ownership and key checks performed by is_authorized_to_pay(). Attackers can submit a known pending invoice ID via maybe_use_invoice to read checkout pricing details and initiate a checkout workflow, resulting in an unauthorized state change of the invoice to on-hold.
Vulnerability class: IDOR (Insecure Direct Object Reference)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- WordPress Changelog (release-notes, patch)
- VulnCheck Advisory: GetPaid WordPress Plugin < 2.8.63 Authorization Bypass via maybe_use_invoice (third-party-advisory)
Frequently asked questions
- What is CVE-2026-119748?
- CVE-2026-119748 is a medium-severity vulnerability in Ayecode Ltd Payment Forms, Buy Now Buttons, And Invoicing System | Getpaid, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 6.5/10. Published 2026-11-04.
- How severe is CVE-2026-119748?
- Medium severity. CVSS v3 base score is 6.5 out of 10.