CVE-2025-14880

Netcash WooCommerce Payment Gateway <= 4.1.3 - Missing Authorization to Unauthenticated Order Status Modification

Published Jan 14, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The Netcash WooCommerce Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_return_url function in all versions up to, and including, 4.1.3. This makes it possible for unauthenticated attackers to mark any WooCommerce order as processing/completed.

Analysis

AI-generated

Technical impact

The Netcash WooCommerce Payment Gateway plugin for WordPress contains a missing capability check in the handle_return_url function for all releases up to and including 4.1.3. This flaw permits unauthenticated attackers to trigger the return URL endpoint and set any WooCommerce order status to processing or completed, effectively advancing orders without valid authorization. The vulnerability meets the criteria for CWE‑862, indicating a missing privileged access check that results in unauthorized modifications of application state.

Affected Systems

Sites that have installed Netcash WooCommerce Payment Gateway version 4.1.3 or earlier are vulnerable. The issue applies to the WordPress plugin as shipped in those releases, meaning any WooCommerce installation that relies on that plugin for payment processing is at risk.

Risk and Exploitability

The CVSS score of 5.3 classifies this as moderate risk, while the EPSS score of <1% indicates a very low probability of exploitation at present. The flaw is not listed in the CISA KEV catalog. Based on the description, it is inferred that the handle_return_url function can be called via the payment gateway's callback, allowing an unauthenticated requester to manipulate the order status without needing credentials. The absence of a proper capability check means the attacker can control the status change directly, potentially enabling fraudulent order fulfillment or masking unauthorized activity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Netcash WooCommerce Payment Gateway to a version that implements the required capability check for the handle_return_url function.
  • If an immediate update is not feasible, block or limit unauthenticated access to the plugin’s return URL endpoint by configuring web server rules or a security plugin to allow access only to authenticated users and verified callbacks.
  • Enable detailed logging for order status changes and routinely monitor logs for any unexpected status updates that might indicate attempts to manipulate order states from unauthenticated origins.

Generated by OpenCVE AI on April 21, 2026 at 16:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Netcashpaynow
Netcashpaynow netcash Woocommerce Payment Gateway
Wordpress
Wordpress wordpress
Vendors & Products Netcashpaynow
Netcashpaynow netcash Woocommerce Payment Gateway
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Description The Netcash WooCommerce Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_return_url function in all versions up to, and including, 4.1.3. This makes it possible for unauthenticated attackers to mark any WooCommerce order as processing/completed.
Title Netcash WooCommerce Payment Gateway <= 4.1.3 - Missing Authorization to Unauthenticated Order Status Modification
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Apr 8, 2026, 4:59 PM
Reserved
Dec 18, 2025, 11:31 AM
Status
Deferred
Published
Jan 14, 2026, 6:15 AM
Modified
Jun 17, 2026, 8:36 AM