HomeWordPress vulnerabilitiesPayPlus Payment Gateway
PayPlus Payment Gateway vulnerabilities
PayPlus Payment Gateway has 4 known vulnerabilities in this database. The most recent published record is dated 20 Nov 2026.
- Known vulnerabilities
- 4
- Active installs
- 1,000+
- Latest version
- 8.3.2
- Last updated
- 8 Nov 2026
- Most recent
- 20 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
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-129185 | Medium 4.3 | Up to 8.3.4 | No fixed version yet | 2 d ago |
| Broken access control CVE-2026-12972 | Medium 5.3 | Before 8.2.2 | Fixed in 8.2.2 | 20 Jul 2026 |
| Broken access control CVE-2026-12973 | Medium 6.5 | Before 8.2.2 | Fixed in 8.2.2 | 20 Jul 2026 |
| SQL injection CVE-2024-6205 | Critical 9.8 | Before 6.6.9 | Fixed in 6.6.9 | 19 Jul 2024 |
Read the published descriptions
- CVE-2026-129185, 20 Nov 2026
- The PayPlus Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 8.3.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to generate PayPlus payment page links for arbitrary WooCommerce orders belonging to any customer, overwrite those orders' payment method and PayPlus-related order meta, and trigger PayPlus API calls using the store's credentials - including, when a POS EMV device is configured, initiating a charge request to the store's physical POS terminal. The exploit requires no nonce and no special capability beyond being logged in, as the authorization block is unreachable on the AJAX path due to the inverted isset() predicate. CVE record
- CVE-2026-12972, 20 Jul 2026
- The PayPlus Payment Gateway WordPress plugin before 8.2.2 does not perform authorization or order-ownership validation in one of its AJAX actions available to unauthenticated users, allowing them to tamper with the payment-related metadata of arbitrary WooCommerce orders. CVE record
- CVE-2026-12973, 20 Jul 2026
- The PayPlus Payment Gateway WordPress plugin before 8.2.2 does not perform authorization or order-ownership validation in one of its AJAX actions available to unauthenticated users, allowing them to disclose the secret order key of arbitrary WooCommerce orders and, under some configurations, to modify order statuses. CVE record
- CVE-2024-6205, 19 Jul 2024
- The PayPlus Payment Gateway WordPress plugin before 6.6.9 does not properly sanitise and escape a parameter before using it in a SQL statement via a WooCommerce API route available to unauthenticated users, leading to an SQL injection vulnerability. CVE record
What to do if you run PayPlus Payment Gateway
If you run PayPlus Payment Gateway, 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 PayPlus Payment Gateway vulnerabilities
Free. We email you when a new vulnerability is published for PayPlus Payment Gateway, 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.