dbcve.org
MultivendorxWordPress extension

CVE-2025-2789

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-05
Fix available
A fix is available. Upgrade to 4.2.20 or later.
See remediation →
74/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
The MultiVendorX – Empower Your WooCommerce Store with a Dynamic Multivendor Marketplace – Build the Next Amazon, eBay, Etsy plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the delete_table_rate_shipping_row function in all versions up to, and including, 4.2.19. This makes it possible for unauthenticated attackers to delete Table Rates that can impact the shipping cost calculations.

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 a missing capability check on the delete_table_rate_shipping_row function, allowing unauthenticated attackers to delete shipping table rates. This Insecure Direct Object Reference (IDOR) vulnerability affects all versions up to 4.2.19 and can impact shipping cost calculations.

MitigationUpdate the MultiVendorX plugin to version 4.2.20 or later when a patch is released. Until then, consider disabling the affected shipping features or deploying a WAF rule to block the vulnerable endpoint.

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

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

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

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. Verify MultiVendorX plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate MultiVendorX (or check wp-content/plugins/ for mvx-directory). Note the installed version displayed.
    Affected if MultiVendorX plugin is installed and version is below 4.2.20
  2. Confirm plugin version number
    Access the plugin file header (typically in main plugin file like mvx.php) or use wp-cli: wp plugin list --plugin=mvx --format=table. Compare the version against 4.2.20.
    Affected if Version is below 4.2.20 (e.g., 4.2.19, 4.2.18, etc.)
  3. Check if shipping table rates feature is active
    Navigate to MultiVendorX settings in WordPress admin: MVX Vendor Dashboard > Settings > Shipping. Inspect whether table rate shipping options are configured or enabled for vendors.
    Affected if Table rate shipping feature is enabled or any shipping rates are configured in the system
  4. Verify vulnerable endpoint accessibility
    Check for the presence of the delete_table_rate_shipping_row function in the plugin code (search in wp-content/plugins/mvx/includes/*.php). This function handles the vulnerable AJAX/action call.
    Affected if The function delete_table_rate_shipping_row exists in the plugin codebase without capability checks (verified by code review or presence of the endpoint in network logs)

User is affected if MultiVendorX plugin version is below 4.2.20 AND the table rate shipping feature is active in the WooCommerce multivendor environment.

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.20 or later
Fixed in 4.2.20
Interim mitigation

Update the MultiVendorX plugin to version 4.2.20 or later when a patch is released. Until then, consider disabling the affected shipping features or deploying a WAF rule to block the vulnerable endpoint.

Recommended fix High confidence

4.2.20

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins section
  3. Locate the MultiVendorX plugin in the installed plugins list
  4. Click 'Update now' on the MultiVendorX plugin if an update is available, or manually upload version 4.2.20
  5. Verify the plugin version is showing 4.2.20 or higher after updating
  6. Test the Table Rates shipping functionality in the WooCommerce shipping settings to confirm it operates correctly

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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