MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution <= 4.2.14 - Unauthenticated Limited Local File Inclusion
Strategic Overview
- Status
- Patched in 4.2.15
- Affected Version
<= 4.2.14- CVSS
- 9.8Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-0493
At a glance
CVE-2025-0493 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 4.2.14. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.2.15; sites on affected versions should update now. Disclosed January 2025, reported by mikemyers.
Vulnerability Overview
The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to Limited Local File Inclusion in all versions up to, and including, 4.2.14 via the tabname parameter. This makes it possible for unauthenticated attackers to include PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where PHP files can be uploaded and included
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, integrity, availability — full site compromise territory.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in MultiVendorX <= 4.2.14 takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For MultiVendorX the fix is 4.2.15: builds <= 4.2.14 are affected, anything from 4.2.15 onward is not.
Remediation
Update to version 4.2.15, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MultiVendorX 4.2.15 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
- 9.8CVE-2024-8289: MultiVendorX Limited Vendor Privilege
CVE-2024-8289 - 8.8CVE-2022-2657: Multivendor Marketplace Solution… CSRF
CVE-2022-2657 - 8.6CVE-2024-24703: MultiVendorX Marketplace Missing Authorization
CVE-2024-24703 - 8.6MultiVendorX <= 4.0.25 Improper Authorization on REST Routes
- 8.2Multivendor Marketplace Solution for WooCommerce – WC Marketplace LFI
- 7.5CVE-2024-8289: MultiVendorX Arbitrary Vendor Deletion
CVE-2024-8289 - 7.5CVE-2023-51355: WC Marketplace <= 4.0.23 Missing Authorization
CVE-2023-51355 - 7.3CVE-2022-2657: Multivendor… Multiple Unprotected AJAX Actions
CVE-2022-2657
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C