dbcve.org
MultivendorxWordPress extension

CVE-2024-31304

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 4.1.4 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 MultiVendorX WC Marketplace.This issue affects WC Marketplace: from n/a through 4.1.3.

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 the MultiVendorX WC Marketplace WordPress plugin (versions through 4.1.3) allows unauthorized users to perform actions that should require proper capability checks or authentication, potentially enabling privilege escalation or unauthorized marketplace operations.

MitigationUpdate WC Marketplace to the latest patched version. Until a patch is available, review and restrict user capabilities, implement additional authorization checks on affected endpoints, and monitor for suspicious administrative or vendor-level actions.

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.1.4

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. Check MultiVendorX plugin version
    In WordPress admin, go to Plugins > Installed Plugins > MultiVendorX and read the version number. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/wc-multivendor-marketplace/) for the 'Version' header in the plugin comments, or inspect the readme.txt file.
    Affected if The installed version is lower than 4.1.4 (e.g., 4.1.3 or earlier)
  2. Confirm plugin folder name
    Navigate to wp-content/plugins/ in the WordPress installation directory and locate the plugin folder. The plugin may be named 'wc-multivendor-marketplace', 'wc-marketplace', 'multivendorx', or similar.
    Affected if The folder exists and contains the MultiVendorX plugin files, indicating the plugin is installed.
  3. Identify if vendor/admin capabilities are misconfigured
    In WordPress admin, go to Users > Roles or use a role editor plugin to examine capabilities assigned to Vendor or Subscriber roles. Check if any users with low-level roles (like Subscriber) have unexpectedly elevated capabilities such as 'manage_options', 'manage_vendor_settings', or vendor-related capabilities they should not possess.
    Affected if Users with Subscriber or Customer roles possess administrative or vendor management capabilities they should not have.
  4. Review access logs for unauthorized vendor actions
    Examine WordPress activity logs, server access logs, or security plugin logs for requests to vendor-related endpoints (typically /wp-admin/admin-ajax.php?action=... or custom vendor endpoints) performed by users with Subscriber or Customer roles.
    Affected if Requests to vendor management endpoints originate from non-administrator, non-vendor user accounts.

A user is affected if the MultiVendorX plugin version is below 4.1.4 AND the WordPress site has users with roles below Administrator who can perform vendor or administrative actions they should not be able to perform.

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.1.4 or later
Fixed in 4.1.4
Interim mitigation

Update WC Marketplace to the latest patched version. Until a patch is available, review and restrict user capabilities, implement additional authorization checks on affected endpoints, and monitor for suspicious administrative or vendor-level actions.

Recommended fix Moderate confidence

4.1.4

  1. 1. Back up your WordPress database and files before performing any upgrade.
  2. 2. Navigate to the WordPress admin dashboard for your site.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find MultiVendorX (WC Marketplace) in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.1.4.
  6. 6. Alternatively, download version 4.1.4 from the official WordPress plugin repository or your account at MultivendorX/WC Marketplace.
  7. 7. If using a manual update, deactivate the current plugin, delete it (data should be preserved if configured correctly), then upload and install version 4.1.4.
  8. 8. After upgrade, verify the authorization controls are functioning correctly and test vendor capabilities.

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

Fix this in Multivendorx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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