CVE-2024-9943

MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution <= 4.2.4 - Cross-Site Request Forgery to Vendor Updates

2024-10-23 19:21
wesley (wcraft)

Strategic Overview

Status
Patched in 4.2.5
Affected Plugin
MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
Affected Version
<= 4.2.4
CVSS
6.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-9943
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

CVE-2024-9943 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 4.2.4. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.2.5; sites on affected versions should update now. Disclosed October 2024, reported by wesley (wcraft).

Vulnerability Overview

The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.2.4. This is due to missing or incorrect nonce validation on several functions in api/class-mvx-rest-controller.php. This makes it possible for unauthenticated attackers to update vendor account details, create vendor accounts, and delete arbitrary users via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in MultiVendorX <= 4.2.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For MultiVendorX the fix is 4.2.5: builds <= 4.2.4 are affected, anything from 4.2.5 onward is not.

Remediation

Update to version 4.2.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to MultiVendorX: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MultiVendorX 4.2.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-9943https://www.wordfence.com/threat-intel/vulnerabilities/id/b950faf9-2122-42af-9f05-ec850767be32https://nvd.nist.gov/vuln/detail/CVE-2024-9943

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C