dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14880

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Netcash WooCommerce Payment Gateway plugin lacks proper authorization validation on the handle_return_url function, allowing unauthenticated attackers to directly manipulate WooCommerce order statuses (mark orders as processing or completed) without any capability check.

MitigationUpdate the plugin to version 4.1.4 or later which includes proper capability checks. Until then, consider disabling the plugin or adding web application firewall rules to block suspicious return URL manipulations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Netcash WooCommerce Payment Gateway is installed
    Check the WordPress plugin directory for the Netcash WooCommerce Payment Gateway plugin. In the filesystem, look in wp-content/plugins/ for a folder named 'wc-gateway-netcash', 'netcash-woocommerce', or similar Netcash-related plugin directories.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Determine the installed plugin version
    Read the main plugin file (usually plugin-name.php) in the Netcash plugin folder and look for the 'Version:' header in the file comment, or check the WordPress plugin admin page for the installed version.
    Affected if The installed version is lower than 4.1.4 or the version cannot be determined (indicating an unpatched older version)
  3. Inspect the handle_return_url function for capability checks
    Open the main plugin PHP file and search for the function 'handle_return_url'. Examine the function to see if it includes a capability check such as 'current_user_can' or 'wp_verify_nonce' before processing order status changes.
    Affected if The function lacks any capability verification or nonce validation before modifying order statuses
  4. Check access to the return URL endpoint
    Identify the hook/register for handle_return_url (commonly add_action('init', 'handle_return_url') or similar). Attempt to access the registered endpoint/URL directly without authentication to see if the request is processed.
    Affected if The return URL handler processes requests without requiring authentication or valid nonce tokens

A user is affected if the Netcash WooCommerce Payment Gateway plugin is installed with a version before 4.1.4 AND the handle_return_url function processes requests without capability checks, allowing unauthenticated order status manipulation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 4.1.4 or later which includes proper capability checks. Until then, consider disabling the plugin or adding web application firewall rules to block suspicious return URL manipulations.

Recommended fix Moderate confidence

Version 4.1.4 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Netcash WooCommerce Payment Gateway' plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update the plugin to the latest version (version 4.1.4 or higher)
  6. 6. Verify the update completed successfully
  7. 7. Test that WooCommerce orders can be processed normally

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14880 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14880 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data