Piraeus Bank WooCommerce Payment Gateway <= 3.1.4 - Missing Authorization to Unauthenticated Arbitrary Order Status Change
Strategic Overview
- Status
- Patched in 3.1.5
- Affected Plugin
- Piraeus Bank WooCommerce Payment Gateway
- Affected Version
<= 3.1.4- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-14460
At a glance
CVE-2025-14460 is a medium-severity Missing Authorization vulnerability in the Piraeus Bank WooCommerce Payment Gateway WordPress plugin, affecting versions <= 3.1.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.5; sites on affected versions should update now. Disclosed January 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Piraeus Bank WooCommerce Payment Gateway <= 3.1.4 carries this weakness at fail, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Piraeus Bank WooCommerce Payment Gateway the fix is 3.1.5: builds <= 3.1.4 are affected, anything from 3.1.5 onward is not.
Remediation
Update to version 3.1.5, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Piraeus Bank WooCommerce Payment Gateway 3.1.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Piraeus Bank WooCommerce Payment Gateway
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C