Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14460: CWE-862 Missing Authorization in enartia Piraeus Bank WooCommerce Payment Gateway

0
Medium
VulnerabilityCVE-2025-14460cvecve-2025-14460cwe-862
Published: Wed Jan 07 2026 (01/07/2026, 09:21:04 UTC)
Source: CVE Database V5
Vendor/Project: enartia
Product: Piraeus Bank WooCommerce Payment Gateway

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 11:19:17 UTC

Technical Analysis

The vulnerability identified as CVE-2025-14460 affects the Piraeus Bank WooCommerce Payment Gateway plugin for WordPress, specifically all versions up to and including 3.1.4. The root cause is a missing authorization check (CWE-862) on the payment callback endpoint handler that processes the 'fail' callback from the payment gateway. This endpoint is publicly accessible and accepts a MerchantReference parameter, which corresponds to the order ID. Because order IDs are sequential integers, an attacker can easily enumerate valid order IDs and send crafted requests to change any order's status to 'failed' without authentication or user interaction. The vulnerability impacts the integrity of order data but does not affect confidentiality or availability. Exploitation could lead to business disruptions such as canceled shipments, incorrect inventory adjustments, and financial losses due to order failures. The CVSS v3.1 base score is 5.3, reflecting a medium severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed. No patches or exploits are currently documented, but the vulnerability is publicly disclosed and should be addressed promptly.

Potential Impact

This vulnerability can significantly disrupt e-commerce operations for organizations using the affected plugin. By allowing unauthorized modification of order statuses to 'failed,' attackers can cause legitimate orders to be canceled, leading to shipment halts and customer dissatisfaction. Inventory systems relying on order status may become inaccurate, resulting in stock mismanagement and potential overstock or stockouts. Financially, businesses may suffer revenue loss from canceled sales and increased customer support costs. Although the vulnerability does not expose sensitive data or cause system downtime, the integrity compromise can undermine trust in the payment process and damage brand reputation. The ease of exploitation and lack of authentication requirements increase the risk of widespread abuse, especially for high-volume WooCommerce stores using this payment gateway.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately update the Piraeus Bank WooCommerce Payment Gateway plugin once an official patch is released by the vendor. In the absence of a patch, administrators should implement strict access controls on the payment callback endpoint, such as IP whitelisting to allow only trusted payment gateway servers or requiring authentication tokens for callback requests. Monitoring and logging all payment callback requests can help detect suspicious activity or enumeration attempts. Additionally, rate limiting requests to the callback endpoint can reduce the risk of automated attacks. Reviewing and hardening the WooCommerce API permissions to restrict order status modifications to authorized users or processes is also recommended. Finally, educating staff and customers about potential order status anomalies can help in early detection and response.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-10T15:56:31.158Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695e4c147349d0379d7d5801

Added to database: 1/7/2026, 12:05:40 PM

Last enriched: 2/27/2026, 11:19:17 AM

Last updated: 3/24/2026, 8:16:47 AM

Views: 96

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses