dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14971

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-27
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 Link Invoice Payment for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the createPartialPayment and cancelPartialPayment functions in all versions up to, and including, 2.8.0. This makes it possible for unauthenticated attackers to create partial payments on any order or cancel any existing partial payment via ID enumeration.

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 Link Invoice Payment for WooCommerce plugin lacks proper capability checks on the createPartialPayment and cancelPartialPayment functions, allowing unauthenticated attackers to manipulate partial payments on any order by enumerating order IDs. This is a broken access control vulnerability (CWE-862) where the plugin fails to verify user permissions before executing sensitive payment operations.

MitigationUpdate to version 2.8.1 or later which includes proper capability checks. Alternatively, implement nonce verification and current_user_can() checks on the affected functions to ensure only authorized users can create or cancel partial payments.

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 the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > look for 'Link Invoice Payment for WooCommerce' and note the version number displayed. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is lower than 2.8.1 (the patched version).
  2. Verify the plugin is active
    In WordPress admin > Plugins, confirm that 'Link Invoice Payment for WooCommerce' shows as 'Active'.
    Affected if The plugin is active and the version is below 2.8.1.
  3. Check if partial payment functions exist in the codebase
    Access the plugin directory via file manager or FTP, locate the main plugin file (usually link-invoice-payment-for-woocommerce.php or similar), and search for 'createPartialPayment' and 'cancelPartialPayment' function definitions.
    Affected if These functions exist without proper capability checks (no current_user_can() validation before execution).
  4. Inspect the vulnerable functions for capability checks
    Open the PHP file containing createPartialPayment and cancelPartialPayment. Look for 'current_user_can' or 'nonce verification' before any payment manipulation logic.
    Affected if The functions lack current_user_can() checks or nonce verification, allowing unauthenticated access.
  5. Determine if WooCommerce orders can be accessed externally
    Test if an unauthenticated request to create or cancel a partial payment can be crafted (for example, by checking if the plugin registers REST API routes or AJAX actions without proper authorization callbacks).
    Affected if The plugin exposes payment manipulation endpoints accessible without authentication.

If the plugin version is below 2.8.1 and the createPartialPayment/cancelPartialPayment functions lack current_user_can() checks, the site is vulnerable to unauthenticated partial payment 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 to version 2.8.1 or later which includes proper capability checks. Alternatively, implement nonce verification and current_user_can() checks on the affected functions to ensure only authorized users can create or cancel partial payments.

Recommended fix Moderate confidence

Version 2.8.1 or later (verify latest version on WordPress plugin repository)

  1. Check the WordPress plugin repository for the Link Invoice Payment for WooCommerce plugin
  2. Navigate to Plugins > Add New > Upload or search for the plugin in the WordPress admin
  3. If an update to version 2.8.1 or later is available, click Update Now
  4. Alternatively, download the latest version from plugins.trac.wordpress.org and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14971 — 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-14971 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