CVE-2026-119749AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System unchecked quantity
CVE-2026-119749 is a unchecked quantity in AyeCode Ltd Payment forms, Buy now buttons, and Invoicing System, rated high (8.7 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
A count or size from input is not checked before it is used.
How it is reached
An attacker can exploit it over the network, without an 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 drive the component into behaviour its authors did not intend.
Is it being exploited?
There is no public report of exploitation yet. It can be exploited automatically, at scale. EPSS estimates a 0.36% chance of exploitation activity in the next 30 days, higher than 30% 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, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
The GetPaid plugin for WordPress before 2.8.63 contains an improper input validation vulnerability that allows unauthenticated attackers to bypass payment processing by submitting a negative item quantity on a public payment form. Attackers can exploit the unchecked quantity value in process_item() to produce a negative line subtotal that reduces the invoice total to zero, causing process_free_payment() to mark the invoice as paid without any actual gateway charge.
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.
- Interfaces that accept external input. The flaw sits at the input boundary of the affected component.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.
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.