CVE-2026-119747AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System incorrect authorization
CVE-2026-119747 is a incorrect authorization in AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System, rated high (7.1 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
A permission check exists but gets the answer wrong for some callers.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.21% chance of exploitation activity in the next 30 days, higher than 11% of scored CVEs.
What to do
- Upgrade AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System to 2.8.63 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.