dbcve.org
MultivendorxWordPress extension

CVE-2024-8289

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-04
Fix available
A fix is available. Upgrade to 4.2.1 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
The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to privilege escalation/de-escalation and account takeover due to an insufficient capability check on the update_item_permissions_check and create_item_permissions_check functions in all versions up to, and including, 4.2.0. This makes it possible for unauthenticated attackers to change the password of any user with the vendor role, create new users with the vendor role, and demote other users like administrators to the vendor role.

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 MultiVendorX WooCommerce multivendor plugin has insufficient capability checks on the update_item_permissions_check and create_item_permissions_check REST API functions, allowing unauthenticated attackers to manipulate vendor user accounts. Attackers can change any vendor user's password, create new vendor accounts, and demote administrators to vendor role, achieving full account takeover and privilege escalation.

MitigationUpdate MultiVendorX plugin to version 4.2.1 or later which contains the proper capability validation. If patching is delayed, consider blocking unauthenticated access to the vendor REST API endpoints 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
MultivendorxWordPress extension
Affected:< 4.2.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify MultiVendorX plugin installation and version
    Locate the MultiVendorX plugin directory (commonly at wp-content/plugins/wc-multivendor-marketplace/) and check the main plugin file for the version number, or query the WordPress plugins API/database for the installed version.
    Affected if The installed version is lower than 4.2.1
  2. Confirm REST API endpoint exposure
    Send a GET request to the MultiVendorX REST API endpoints (typically /wp-json/wcmp/v1/ or /wp-json/wc-multivendor/v1/) without authentication headers to verify they are accessible.
    Affected if The REST API endpoints respond without requiring authentication (HTTP 200 OK without 401/403)
  3. Test vendor account manipulation vulnerability
    Send a crafted POST request to the create_item_permissions_check or update_item_permissions_check endpoints without authentication, attempting to modify vendor user data or create a new vendor account.
    Affected if The API accepts the request without returning an authentication or capability error, allowing modification of vendor user data or role changes
  4. Check for existing vendor role users
    Query the WordPress database or user administration panel to identify users assigned the 'vendor' role (or similar roles created by MultiVendorX).
    Affected if Vendor role users exist in the system, making them potential targets for the account takeover vulnerability

A user is affected if MultiVendorX version is below 4.2.1 and the REST API endpoints are accessible without authentication, allowing unauthenticated manipulation of vendor accounts.

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

Update MultiVendorX plugin to version 4.2.1 or later which contains the proper capability validation. If patching is delayed, consider blocking unauthenticated access to the vendor REST API endpoints at the web server level.

Recommended fix High confidence

MultivendorX version 4.2.1

  1. Create a full backup of your WordPress site database and files before proceeding with any updates.
  2. Log in to your WordPress admin dashboard and navigate to Plugins > Installed Plugins.
  3. Find the MultiVendorX plugin in the list and check if an update to version 4.2.1 is available.
  4. If an update is available, click 'Update Now' to install version 4.2.1.
  5. Alternatively, you can update manually by downloading version 4.2.1 from the WordPress Plugin Repository and uploading it via Plugins > Add New > Upload Plugin.
  6. After updating, verify the plugin version shows 4.2.1 in your plugins list.
  7. Test that vendor role permissions are functioning correctly by attempting to create a test vendor account.

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

Fix this in Multivendorx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,660
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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