HomeWordPress vulnerabilitiesPiraeus Bank WooCommerce Payment Gateway
Piraeus Bank WooCommerce Payment Gateway vulnerabilities
Piraeus Bank WooCommerce Payment Gateway has 2 known vulnerabilities in this database. The most recent published record is dated 7 Jan 2026.
- Known vulnerabilities
- 2
- Active installs
- 3,000+
- Latest version
- 3.2.0
- Last updated
- 19 Jan 2026
- Most recent
- 7 Jan 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-2025-14460 | Medium 5.3 | Up to 3.1.4 | Fixed in a later version (latest 3.2.0) | 7 Jan 2026 |
| SQL injection CVE-2024-0610 | Critical 9.8 | Before 1.7.0 | Fixed in 1.7.0 | 17 Feb 2024 |
Read the published descriptions
- CVE-2025-14460, 7 Jan 2026
- The Piraeus Bank WooCommerce Payment Gateway plugin for WordPress is vulnerable to unauthorized order status modification in all versions up to, and including, 3.1.4. This is due to missing authorization checks on the payment callback endpoint handler when processing the 'fail' callback from the payment gateway. This makes it possible for unauthenticated attackers to change any order's status to 'failed' via the publicly accessible WooCommerce API endpoint by providing only the order ID (MerchantReference parameter), which can be easily enumerated as order IDs are sequential integers. This can cause significant business disruption including canceled shipments, inventory issues, and loss of revenue. CVE record
- CVE-2024-0610, 17 Feb 2024
- The Piraeus Bank WooCommerce Payment Gateway plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'MerchantReference' parameter in all versions up to, and including, 1.6.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
What to do if you run Piraeus Bank WooCommerce Payment Gateway
If you run Piraeus Bank WooCommerce 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 Piraeus Bank WooCommerce Payment Gateway vulnerabilities
Free. We email you when a new vulnerability is published for Piraeus Bank WooCommerce 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.