Auth bypass in Ayecode Ltd Payment Forms, Buy Now Buttons, And Invoicing System | Getpaid
CVE-2026-119747
The GetPaid plugin for WordPress before 2.8.63 contains an incorrect authorization vulnerability where the check_post_permissions() method in includes/api/class-getpaid-rest-posts-controller.php maps REST operations to generic WordPress post capabilities instead of enforcing the plugin's manage_invoicing permission. Authenticated users with lower-privileged roles such as Editor or Author can exploit this flaw to list other users' invoices, mark pending invoices as paid without recording payment transactions, or create published items and new invoices through the REST API.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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 Incorrect Authorization via REST API (third-party-advisory)
Frequently asked questions
- What is CVE-2026-119747?
- CVE-2026-119747 is a high-severity vulnerability in Ayecode Ltd Payment Forms, Buy Now Buttons, And Invoicing System | Getpaid, classified under Incorrect Authorization. CVSS score: 7.1/10. Published 2026-11-04.
- How severe is CVE-2026-119747?
- High severity. CVSS v3 base score is 7.1 out of 10.