Multivendor Marketplace Solution for WooCommerce – WC Marketplace <= 3.8.11.8 - Local File Inclusion

2022-08-15 00:00
WPScanTeam

Strategic Overview

Status
Patched in 3.8.12
Affected Plugin
MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
Affected Version
<= 3.8.11.8
CVSS
8.2High
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE pending
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

This record tracks a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 3.8.11.8. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high confidentiality 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 WPScanTeam.

Vulnerability Overview

The Multivendor Marketplace Solution for WooCommerce plugin is vulnerable to Local File Inclusion via the 'wcmp_announcements_refresh_tab_data' unprotected AJAX action in versions up to, and including, 3.8.11.8. This allows unauthenticated attackers to include arbitrary files on the local filesystem, potentially granting access to sensitive information or restricted areas.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

MultiVendorX <= 3.8.11.8 carries this weakness at wcmp_announcements_refresh_tab_data, and reaching it takes a caller who can reach the endpoint. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created 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
  • Scanner
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/4752b3a7-dbb0-4326-bfff-b94dd55b4bf1

Related records

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