Answer in brief
CVE-2026-119747 records a High severity (CVSS 7.1) vulnerability in GetPaid WordPress Plugin < 2.8.63 Incorrect Authorization via REST API. The current sources do not mark it as known exploited. The current feed maps AyeCode Ltd/Payment forms, Buy now buttons, and Invoicing System | GetPaid (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps AyeCode Ltd/Payment forms, Buy now buttons, and Invoicing System | GetPaid (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| AyeCode Ltd/Payment forms, Buy now buttons, and Invoicing System | GetPaidgeneric | >=0 <2.8.63 | 2.8.63 |
Published upstream
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.