Skip to main content
VulnerabilityPublished

CVE-2026-119747: Payment forms, Buy now buttons, and Invoicing System | GetPaid (WordPress plugin) · Incorrect Authorization

Affects Payment forms, Buy now buttons, and Invoicing System | GetPaid (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.8.63 soon.

Data as of 4 Nov 2026, 17:14 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.17.1
Patch
Available – fixed in 2.8.63
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade Payment forms, Buy now buttons, and Invoicing System | GetPaid (WordPress plugin) to 2.8.63.

Affected software

ProductAffectedFixed in
AyeCode LtdPayment forms, Buy now buttons, and Invoicing System | GetPaidAffected
  • <2.8.63
Fixed in
  • 2.8.63

AI-suggested

A fix is available in GetPaid plugin version 2.8.63. Users should upgrade to version 2.8.63 or later to address this incorrect authorization vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-119747 is an authorization vulnerability in the GetPaid WordPress plugin before version 2.8.63. The flaw arises because the plugin incorrectly maps REST API operations to generic WordPress post capabilities instead of enforcing its own manage_invoicing permission. This allows authenticated users with roles such as Editor or Author to access and manipulate invoices beyond their intended privileges, including listing other users' invoices, marking pending invoices as paid without proper transaction records, and creating published items and new invoices via the REST API.

References

Community reviews

Loading reviews…