CVE-2025-14460
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-14460 is a missing authorization vulnerability in the Piraeus Bank WooCommerce Payment Gateway plugin for WordPress that allows unauthenticated attackers to modify any order's status to 'failed'. All plugin versions up to and including 3.1.4 are affected. The vulnerability was disclosed on January 7, 2026, by Wordfence, and carries a CVSS v3.1 base score of 5.3 (Medium) (Wordfence).

Technical details

The root cause is classified as CWE-862 (Missing Authorization). The plugin's payment callback endpoint handler — responsible for processing 'fail' callbacks from the Piraeus Bank payment gateway — does not perform any authorization checks before acting on the request. An unauthenticated attacker can send a crafted HTTP request to the publicly accessible WooCommerce API endpoint, supplying only the MerchantReference parameter (the order ID), which is trivially enumerable because WooCommerce order IDs are sequential integers. The vulnerable code is located in WC_Piraeusbank_Gateway.php at approximately line 821 (Wordfence, Plugin Source).

Impact

Successful exploitation allows any unauthenticated attacker to set any WooCommerce order to a 'failed' status, causing significant business disruption. Consequences include canceled shipments, inventory management issues, and direct revenue loss for affected merchants. There is no confidentiality or availability impact; the vulnerability is limited to integrity of order data, but the business impact can be severe for e-commerce operators relying on the plugin (Wordfence).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the available data. The EPSS score is approximately 0.034%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, the attack requires no authentication, no special privileges, and no user interaction, and the target parameter (order ID) is easily enumerable, making the barrier to exploitation very low (Wordfence).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites using the Piraeus Bank WooCommerce Payment Gateway plugin (version ≤ 3.1.4) via passive scanning, plugin enumeration tools, or by checking publicly visible plugin metadata.
  2. Enumerate order IDs: Since WooCommerce order IDs are sequential integers, begin with low integers (e.g., 1, 2, 3, ...) and increment to enumerate valid order IDs.
  3. Craft the malicious request: Send an HTTP request to the publicly accessible WooCommerce API callback endpoint used by the plugin for 'fail' payment callbacks, supplying the target order ID as the MerchantReference parameter.
  4. Trigger order status change: The plugin processes the unauthenticated 'fail' callback without authorization checks, updating the targeted order's status to 'failed' in the WooCommerce database.
  5. Repeat for disruption: Iterate over a range of order IDs to mass-cancel orders, causing widespread business disruption to the targeted merchant (Wordfence, Plugin Source).

Indicators of compromise

  • Network: Repeated HTTP POST/GET requests to the WooCommerce payment callback endpoint (associated with the Piraeus Bank gateway) from a single or rotating IP address, especially with sequentially incrementing MerchantReference values.
  • Logs: WordPress/WooCommerce access logs showing a high volume of requests to the Piraeus Bank callback URL path with varying numeric MerchantReference parameters in a short time window.
  • Application: Sudden spike in WooCommerce orders transitioning to 'failed' status, particularly across a broad range of order IDs and without corresponding legitimate payment gateway activity.

Mitigation and workarounds

A patch was released in plugin changeset 3439515, which adds proper authorization checks to the payment callback endpoint. Administrators should update the Piraeus Bank WooCommerce Payment Gateway plugin to the version released after 3.1.4 immediately. As a temporary workaround, site administrators can restrict access to the WooCommerce callback endpoint via web server rules (e.g., IP allowlisting to known Piraeus Bank gateway IPs) until the plugin can be updated (Plugin Changeset, Wordfence).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-18039NONEN/A
  • essential-addons-for-elementor-lite
NoYesAug 14, 2026
CVE-2026-16810NONEN/A
  • bit-form
NoYesAug 14, 2026
CVE-2026-16739NONEN/A
  • epeken-all-kurir
NoNoAug 14, 2026
CVE-2026-15205NONEN/A
  • paymob-for-woocommerce
NoYesAug 14, 2026
CVE-2026-14290NONEN/A
  • embed-google-photos-album-easily
NoNoAug 14, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management