CVE-2026-119747: GetPaid WordPress Plugin < 2.8.63 Incorrect Authorization via REST API
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 11% of scored CVEs
DescriptionCVE.org
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.
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
- Vendor
- AyeCode Ltd
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-119747 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.