dbcve.org
Wholesale For WoocommerceWordPress extension · Wpexperts

CVE-2024-30469

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 2.3.1 or later.
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
Missing Authorization vulnerability in WPExperts Wholesale For WooCommerce.This issue affects Wholesale For WooCommerce: from n/a through 2.3.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 vulnerability in the Wholesale For WooCommerce WordPress plugin (versions up to 2.3.0). The plugin fails to properly enforce authorization checks, potentially allowing unauthenticated or low-privilege users to access functionality they should not have permission to use.

MitigationUpdate Wholesale For WooCommerce to the latest version beyond 2.3.0 which contains the authorization fix. If no update is available, review the plugin code and implement proper capability checks and nonce validations for all sensitive operations.

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
Wholesale For WoocommerceWordPress extension
Affected:< 2.3.1

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wholesale For WooCommerce' by Wpexperts, or check the plugin folder /wp-content/plugins/wholesale-for-woocommerce/ and read the main PHP file's header for the Version field
    Affected if The installed version is below 2.3.1 (e.g., 2.3.0 or any version listed as < 2.3.1)
  2. Verify plugin is active
    Check if Wholesale For WooCommerce is listed as active in Plugins > Installed Plugins. Alternatively, query the wp_options table for option_name = 'active_plugins' and check for the plugin's directory name
    Affected if The plugin is active and the version is below 2.3.1, exposing the authorization flaw to site visitors and low-privilege users
  3. Inspect user role capabilities
    Navigate to WooCommerce > Wholesale > User Roles (if accessible) or check wp_usermeta for users with 'wholesale_customer' or custom wholesale roles. Also review any public-facing wholesale registration or pricing endpoints
    Affected if Unauthenticated visitors or users with low-privilege roles (like customer) can access wholesale pricing, bulk order forms, or admin-level wholesale configuration pages

You are affected if Wholesale For WooCommerce is installed and active at any version below 2.3.1, as the missing authorization check allows unauthorized access to sensitive wholesale functionality.

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 2.3.1 or later
Fixed in 2.3.1
Interim mitigation

Update Wholesale For WooCommerce to the latest version beyond 2.3.0 which contains the authorization fix. If no update is available, review the plugin code and implement proper capability checks and nonce validations for all sensitive operations.

Recommended fix High confidence

Wholesale For WooCommerce 2.3.1

  1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. Locate Wholesale For WooCommerce in the plugin list
  3. Check if the current version is below 2.3.1
  4. If update available, click 'Update Now' to upgrade to version 2.3.1
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 2.3.1
  6. After updating, verify the plugin is functioning correctly and the vulnerability is resolved

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

Fix this in Wholesale For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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