CVE-2026-119748: GetPaid WordPress Plugin < 2.8.63 Authorization Bypass via maybe_use_invoice
AyeCode Ltd · Payment forms, Buy now buttons, and Invoicing System | GetPaid
Fixed in 2.8.63 · Affected: AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System | GetPaid before 2.8.63 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 14% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- AyeCode Ltd · Payment forms, Buy now buttons, and Invoicing System | GetPaidbefore 2.8.63
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
- Vendor
- AyeCode Ltd
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-119748 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.