HomeWordPress vulnerabilitiesPayment forms, Buy now buttons, and Invoicing System
Payment forms, Buy now buttons, and Invoicing System vulnerabilities
Payment forms, Buy now buttons, and Invoicing System has 8 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 8
- Active installs
- 5,000+
- Latest version
- 2.8.65
- Last updated
- 5 Nov 2026
- Most recent
- 21 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-131971 | Not scored | Before 2.8.63 | Fixed in 2.8.63 | 1 d ago |
| Security weakness CVE-2026-119749 | High 7.5 | Before 2.8.63 | Fixed in 2.8.63 | 4 Nov 2026 |
| Broken access control CVE-2026-119748 | Medium 6.5 | Before 2.8.63 | Fixed in 2.8.63 | 4 Nov 2026 |
| Broken access control CVE-2026-119747 | High 7.1 | Before 2.8.63 | Fixed in 2.8.63 | 4 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-115609 | High 7.1 | Up to 2.8.62 | Fixed in a later version (latest 2.8.65) | 28 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-111110 | High 7.2 | Up to 2.8.61 | Fixed in a later version (latest 2.8.65) | 17 Oct 2026 |
| File inclusion CVE-2026-17605 | Medium 6.6 | Up to 2.8.56 | Fixed in a later version (latest 2.8.65) | 1 Aug 2026 |
| Content injection CVE-2021-47948 | Medium 5.4 | Not yet published | Check for an update | 10 May 2026 |
Read the published descriptions
- CVE-2026-131971, 21 Nov 2026
- The Payment forms, Buy now buttons, and Invoicing System | GetPaid WordPress plugin before 2.8.63 does not check that the visitor is allowed to view an invoice before rendering it through its single-invoice shortcode, and its payment-form embed page lets unauthenticated users render that shortcode for any invoice ID, disclosing customers' names, billing addresses, phone numbers, line items and payment status. CVE record
- CVE-2026-119749, 4 Nov 2026
- 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. CVE record
- CVE-2026-119748, 4 Nov 2026
- The GetPaid plugin for WordPress before 2.8.63 contains an authorization bypass vulnerability that allows unauthenticated attackers to access and manipulate another user's invoice by supplying its ID through the maybe_use_invoice parameter in process_invoice(), bypassing the ownership and key checks performed by is_authorized_to_pay(). Attackers can submit a known pending invoice ID via maybe_use_invoice to read checkout pricing details and initiate a checkout workflow, resulting in an unauthorized state change of the invoice to on-hold. CVE record
- CVE-2026-119747, 4 Nov 2026
- 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. CVE record
- CVE-2026-115609, 28 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Stiofan GetPaid invoicing allows Stored XSS.This issue affects GetPaid: from n/a through 2.8.62. CVE record
- CVE-2026-111110, 17 Oct 2026
- The Payment forms, Buy now buttons, and Invoicing System | GetPaid plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mmdwqzpoxadd' parameter in all versions up to, and including, 2.8.61 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The required nonce (getpaid_form_nonce) is publicly emitted to all visitors via wp_localize_script as WPInv.formNonce, meaning no authentication or prior nonce leak is needed; the stored payload fires when an administrator views the affected invoice's Payment Form Details metabox. CVE record
- CVE-2026-17605, 1 Aug 2026
- 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. CVE record
- CVE-2021-47948, 10 May 2026
- WordPress GetPaid Plugin 2.4.6 contains an HTML injection vulnerability that allows authenticated attackers to inject arbitrary HTML code by exploiting the Help Text field in payment forms. Attackers can inject malicious HTML including image tags and scripts into the Help Text field during payment form creation, which gets stored in the database and executed in the browser when the form is viewed. CVE record
What to do if you run Payment forms, Buy now buttons, and Invoicing System
If you run Payment forms, Buy now buttons, and Invoicing System, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Payment forms, Buy now buttons, and Invoicing System vulnerabilities
Free. We email you when a new vulnerability is published for Payment forms, Buy now buttons, and Invoicing System, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.