Vulnerabilities and security researches forinvoicing invoicing
Direction: ascendingJun 06, 2024
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2021-24369
- CVE, Research URL
- Date
- Jun 22, 2021
- Research Description
- In the GetPaid WordPress plugin before 2.3.4, users with the contributor role and above can create a new Payment Form, however the Label and Help Text input fields were not getting sanitized properly. So it was possible to inject malicious content such as img tags, leading to a Stored Cross-Site Scripting issue which is triggered when the form will be edited, for example when an admin reviews it and could lead to privilege escalation.
- Affected versions
-
max 2.3.4.
- Status
-
vulnerable
Sep 01, 2024
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2024-43973
- CVE, Research URL
- Date
- Nov 01, 2024
- Research Description
- Missing Authorization vulnerability in Stiofan GetPaid invoicing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GetPaid: from n/a through <= 2.8.11.
- Affected versions
-
max 2.8.12.
- Status
-
vulnerable
May 12, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2021-47948
- CVE, Research URL
- Date
- May 10, 2026
- Research Description
- 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.
- Affected versions
-
max 2.4.6.
- Status
-
vulnerable
Aug 02, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-17605
- CVE, Research URL
- Date
- Aug 01, 2026
- Research Description
- 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.
- Affected versions
-
max 2.8.57.
- Status
-
vulnerable
Aug 08, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-12901
- CVE, Research URL
- Date
- Aug 07, 2026
- Research Description
- The GetPaid WordPress plugin before 2.8.55 does not verify the authenticity of incoming Worldpay payment notifications, allowing unauthenticated attackers to forge a notification that marks a pending invoice as paid without any payment being made.
- Affected versions
-
max 2.8.55.
- Status
-
vulnerable
Oct 18, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-111110
- CVE, Research URL
- Date
- Oct 17, 2026
- Research Description
- 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.
- Affected versions
-
max 2.8.62.
- Status
-
vulnerable
Oct 30, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-115609
- CVE, Research URL
- Date
- Oct 28, 2026
- Research Description
- 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.
- Affected versions
-
max 2.8.63.
- Status
-
vulnerable
Nov 06, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-119747
- CVE, Research URL
- Date
- Nov 04, 2026
- Research Description
- 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.
- Affected versions
-
max 2.8.63.
- Status
-
vulnerable
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-119749
- CVE, Research URL
- Date
- Nov 04, 2026
- Research Description
- 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.
- Affected versions
-
max 2.8.63.
- Status
-
vulnerable
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-119748
- CVE, Research URL
- Date
- Nov 04, 2026
- Research Description
- 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.
- Affected versions
-
max 2.8.63.
- Status
-
vulnerable
Nov 13, 2026
Payment forms, Buy now buttons and Invoicing System | GetPaid # CVE-2026-123668
- CVE, Research URL
- Date
- Nov 11, 2026
- Research Description
- The GetPaid WordPress plugin from 2.8.63 to 2.8.64 does not ensure item quantities on its payment forms are whole numbers, allowing unauthenticated users to have an invoice for a priced item marked as paid without being charged.
- Affected versions
-
Min 2.8.63, max 2.8.65.
- Status
-
vulnerable