dbcve.org
Woocommerce Account FundsWordPress extension · Yithemes

CVE-2024-30470

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 1.34.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in YITH YITH WooCommerce Account Funds Premium.This issue affects YITH WooCommerce Account Funds Premium: from n/a through 1.33.0.

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 · moderate confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the YITH WooCommerce Account Funds Premium plugin. The specific affected functionality and attack vector are not detailed in available sources, but the high CVSS score (8.8) indicates that authenticated users with limited privileges can likely access administrative functions or perform unauthorized fund transfers/deposits that should require higher-level permissions.

MitigationImplement proper capability checks and authorization validation on all sensitive functions within the plugin, ensuring that actions like fund transfers, deposits, or account modifications verify both user authentication and appropriate role-based permissions before execution.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce Account FundsWordPress extension
Affected:< 1.34.0

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
High
Integrity
High
Availability
High

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

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. Confirm YITH WooCommerce Account Funds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'YITH WooCommerce Account Funds Premium' or 'YITH WooCommerce Account Funds'. Alternatively, check the plugin files in wp-content/plugins/ for a folder containing 'yith-woocommerce-account-funds'.
    Affected if The plugin is not installed or not present in the WordPress installation.
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view its details, or open the main plugin PHP file (usually includes a version constant) and locate the version number.
    Affected if The installed version is earlier than 1.34.0 (any version < 1.34.0 is affected).
  3. Verify the Account Funds feature is active
    Navigate to YITH > Account Funds in the WordPress admin sidebar. Check if the plugin is enabled and if options related to allowing customers to deposit funds are turned on.
    Affected if The plugin is active and the fund deposit/transfer functionality is enabled for users.
  4. Inspect user role permissions for fund operations
    Check WordPress user roles and capabilities. In WooCommerce, go to WooCommerce > Settings > Account > Account funds section, or check YITH plugin settings to see which user roles can perform fund deposits, transfers, or account fund modifications.
    Affected if Standard customer or subscriber roles are granted permissions to deposit funds or transfer funds without proper admin-level authorization checks.

You are affected if the YITH WooCommerce Account Funds plugin is installed with any version below 1.34.0 and the fund deposit/transfer feature is enabled, allowing lower-privileged users to perform actions that should require higher permissions.

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
Upgrade available Upgrade to 1.34.0 or later
Fixed in 1.34.0
Interim mitigation

Implement proper capability checks and authorization validation on all sensitive functions within the plugin, ensuring that actions like fund transfers, deposits, or account modifications verify both user authentication and appropriate role-based permissions before execution.

Recommended fix High confidence

1.34.0

  1. Backup the WordPress database and files before updating
  2. Update the YITH WooCommerce Account Funds Premium plugin to version 1.34.0 or later via the WordPress admin dashboard ( navigate to Plugins > Installed Plugins > YITH WooCommerce Account Funds Premium > Update Now)
  3. Alternatively, update via WP-CLI: wp plugin update yith-woocommerce-account-funds-premium
  4. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  5. Test account funds functionality (deposit, transfer, balance display) to confirm normal operation

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

Fix this in Woocommerce Account Funds Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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