WordPress security by component
GetPaid
GetPaid (invoicing) is a WordPress plugin with 3 published CVE records in this archive. The latest tracked vulnerability was published Aug 01, 2026; the highest published CVSS base score is 7.5.
Plugin slug:
invoicingLatest vulnerability
CVE-2026-17605: GetPaid payment-form elements let Administrators include PHP files
GetPaid through 2.8.56 lets an Administrator-controlled value select a local file in getpaid_payment_form_element(). An Administrator can include and execute an arbitrary PHP file already present on the server, yielding code execution when another path permits that PHP file to be uploaded.
| Safe version |
|
||
|---|---|---|---|
| Aug 01, 2026 |
CVE-2026-17605
GetPaid payment-form elements let Administrators include PHP files
GetPaid through 2.8.56 lets an Administrator-controlled value select a local file in getpaid_payment_form_element(). An Administrator can include and execute an arbitrary PHP file already present on the server, yielding code execution when another path permits that PHP file to be uploaded.
|
> 2.8.56 |
CVE6.6
NVDPending
|
| Jun 15, 2026 |
CVE-2026-49064
GetPaid: A security weakness
GetPaid is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.8.49.
|
2.8.50 |
CVE7.5
NVDPending
|
| May 10, 2026 |
CVE-2021-47948
Payments Plugin GetPaid: A security weakness
Payments Plugin GetPaid is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is 2.4.6.
|
See mitigation notes |
CVE5.1
NVDPending
|