Search
Search Results (4 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-111110 | 2 Stiofansisland, Wordpress-extensions | 2 Payment Forms, Buy Now Buttons, And Invoicing System | Getpaid, Getpaid | 2026-11-16 | 7.2 High |
| 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-2026-115609 | 2 Stiofan, Wordpress-extensions | 2 Getpaid, Getpaid | 2026-11-16 | 7.1 High |
| 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-2026-123668 | 1 Wordpress-extensions | 1 Getpaid | 2026-11-12 | 5.3 Medium |
| 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. | ||||
| CVE-2026-12901 | 1 Wordpress-extensions | 1 Getpaid | 2026-11-11 | 5.9 Medium |
| 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. | ||||
Page 1 of 1.