CVE-2026-17605 json
Payment forms, Buy now buttons, and Invoicing System | GetPaid <= 2.8.56 - Authenticated (Administrator+) Local File Inclusion via Payment Form 'type' Element Field
published 3mo ago modified 2mo ago also EUVD-2026-51757
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
The Payment forms, Buy now buttons, and Invoicing System | GetPaid plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.8.56 via the getpaid_payment_form_element function. This makes it possible for authenticated attackers, with administrator-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.
Patch / fix
Is CVE-2026-17605 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- stiofansisland Payment forms, Buy now buttons, and Invoicing System | GetPaid
Classification
- Weakness
-
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
- Technology feeds
References
- github.com /AyeCode/invoicing/commit/80625ba90241840e46b0bc5400f100e6d38ee85c
- wordfence.com /threat-intel/vulnerabilities/id/baca279b-0c42-48a9-930a-8d0525066e0a?source=cve
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.54/includes/wpinv-template-functions.php#L1458
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.56/includes/wpinv-template-functions.php#L1458
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.56/includes/wpinv-template-functions.php#L1432
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.56/includes/admin/meta-boxes/class-getpaid-meta-box-payment-form.php#L131
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.56/includes/admin/class-getpaid-metaboxes.php#L257
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.54/includes/wpinv-template-functions.php#L1432
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.54/includes/admin/meta-boxes/class-getpaid-meta-box-payment-form.php#L131
- plugins.trac.wordpress.org /browser/invoicing/tags/2.8.54/includes/admin/class-getpaid-metaboxes.php#L257
Sources
- CVE List CVE-2026-17605
- NVD CVE-2026-17605
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.