CVE-2022-2657

Multivendor Marketplace Solution for WooCommerce – WC Marketplace <= 3.8.11.8 - Cross-Site Request Forgery

2022-08-04 00:00
moumitahalder

Strategic Overview

Status
Patched in 3.8.12
Affected Version
<= 3.8.11.8
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-2657
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

CVE-2022-2657 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 3.8.11.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.8.12; sites on affected versions should update now. Disclosed August 2022, reported by moumitahalder.

Vulnerability Overview

The Multivendor Marketplace Solution for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.8.11.8. This is due to missing or incorrect nonce validation on the wcmp_suspend_vendor ajax action. This makes it possible for unauthenticated attackers to suspend vendors, via forged request granted they can trick a logged in user 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in MultiVendorX <= 3.8.11.8 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 3.8.12: builds <= 3.8.11.8 are affected, anything from 3.8.12 onward is not.

Remediation

Update to version 3.8.12, 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 3.8.12 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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