dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14450

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Wallet System for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'change_wallet_fund_request_status_callback' function in all versions up to, and including, 2.7.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to manipulate wallet withdrawal requests and arbitrarily increase their wallet balance or decrease other users' balances.

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 Wallet System for WooCommerce plugin has a missing capability check on the 'change_wallet_fund_request_status_callback' function. This allows any authenticated user with Subscriber-level access or higher to call this function and manipulate wallet withdrawal request statuses, enabling arbitrary balance modifications to their own or other users' wallets.

MitigationUpdate the plugin to version 2.7.3 or later which implements proper capability checks. Until then, restrict subscriber-level account creation or monitor for suspicious wallet activity.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Check installed plugin version
    Navigate to WordPress admin > Plugins > Wallet System for WooCommerce and view the version number, or inspect the plugin's main PHP file or readme.txt for the Version header
    Affected if Version is earlier than 2.7.3 (the patch removes the missing capability check vulnerability)
  2. Identify WordPress user roles with subscriber-level access
    Go to WordPress admin > Users and review all user accounts. Check the role assigned to each user - any role at Subscriber level or higher (including Subscriber, Contributor, Author, Editor, Shop Manager, Administrator) provides authenticated access
    Affected if Any user account exists with Subscriber role or higher (even Subscriber role alone is sufficient for exploitation)
  3. Verify the vulnerable function exists in the plugin
    Inspect the plugin files for the function named 'change_wallet_fund_request_status_callback' - typically found in includes/class-wallet-system.php or similar main plugin file. If the function exists and the plugin version is pre-2.7.3, the capability check is missing
    Affected if The function exists in the plugin code and version is before 2.7.3, indicating the missing authorization vulnerability is present

The environment is affected if the Wallet System for WooCommerce plugin version is earlier than 2.7.3 and at least one user account with Subscriber-level access or higher exists on the WordPress site.

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 2.7.3 or later which implements proper capability checks. Until then, restrict subscriber-level account creation or monitor for suspicious wallet activity.

Recommended fix Moderate confidence

Any version newer than 2.7.2 (latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Wallet System for WooCommerce' plugin
  4. Check the current installed version matches 2.7.2 or below
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is newer than 2.7.2
  7. Test that wallet withdrawal request status changes now require proper administrative capabilities

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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