dbcve.org
Product Catalog Mode For WoocommerceWordPress extension · Multivendorx

CVE-2024-25929

CRITICAL · 9.1 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 5.0.6 or later.
See remediation →
100/100
Remediation priority · Urgent
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 MultiVendorX Product Catalog Enquiry for WooCommerce by MultiVendorX.This issue affects Product Catalog Enquiry for WooCommerce by MultiVendorX: from n/a through 5.0.5.

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

Missing authorization vulnerability in MultiVendorX Product Catalog Enquiry for WooCommerce plugin allows unauthenticated or unauthorized users to access protected functionality. The CVSS 9.1 score indicates critical severity, likely enabling unauthorized access to sensitive product inquiry data, admin functions, or submission mechanisms without proper capability checks.

MitigationApply vendor patch immediately - upgrade to version 5.0.6 or later. Until patch is available, disable the Product Catalog Enquiry functionality or restrict access at the web server level.

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
Product Catalog Mode For WoocommerceWordPress extension
Affected:< 5.0.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Confirm MultiVendorX plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'MultiVendorX Product Catalog Mode For Woocommerce' or 'Product Catalog Enquiry for WooCommerce' in the list
    Affected if Plugin is present in the WordPress installation
  2. Identify installed plugin version
    In the Plugins list, click on the plugin to view its details, or check the plugin header file for the Version constant. Alternatively, look in the plugin's main PHP file for 'Version:' in the plugin comment block
    Affected if Version number is present and less than 5.0.6
  3. Verify Product Catalog Enquiry feature is active
    Navigate to WooCommerce > Settings > MultiVendorX Catalog or the plugin's settings page. Look for options related to 'Product Catalog Enquiry', 'Catalog Mode', or 'Enquiry Form' and check if they are enabled
    Affected if The Product Catalog Enquiry functionality is enabled in plugin settings
  4. Test for unauthenticated access to enquiry endpoints
    Using a browser or HTTP tool, attempt to access common enquiry-related URLs such as /?action=mvx_catalog_enquiry or /wp-json/mvx/v1/enquiry without logging in. Check if the server returns data or allows form submission without authentication
    Affected if Requests return product inquiry data, submission succeeds, or admin functions execute without requiring login
  5. Check user role and capability enforcement
    As a non-admin user (or while logged out), attempt to access any catalog enquiry admin functions or view enquiry submissions. Verify that WordPress capability checks are properly enforced
    Affected if Unauthenticated or lower-privileged users can access protected enquiry functionality

Your environment is affected if the MultiVendorX Product Catalog Mode plugin version is below 5.0.6 and the Product Catalog Enquiry feature is enabled, allowing unauthorized access without authentication.

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

Apply vendor patch immediately - upgrade to version 5.0.6 or later. Until patch is available, disable the Product Catalog Enquiry functionality or restrict access at the web server level.

Recommended fix High confidence

5.0.6

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Product Catalog Mode For WooCommerce' (or 'MultiVendorX Product Catalog Enquiry for WooCommerce')
  4. 4. If an update is available, click 'Update Now' to upgrade to version 5.0.6
  5. 5. Alternatively, manually download version 5.0.6 from the WordPress plugin repository or MultiVendorX and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the installed version is 5.0.6 after updating

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

Fix this in Product Catalog Mode For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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