MultiVendorX vendor REST access exposes competing-store financial data
MultiVendorX before 5.0.11 has a REST API endpoint that does not verify that the requested store belongs to the authenticated vendor. A vendor-level user can supply another store's identifier and retrieve that vendor's commission and financial information. This unscored record received deeper review because it provides a low-privilege cross-tenant financial-data disclosure primitive. The CNA does not disclose the route, HTTP method or identifier parameter.
- Component
- MultiVendorX
- Plugin slug
multivendorx- Affected
- < 5.0.11
- Safe version
5.0.11- Published
- Aug 05, 2026
This CVE was published Aug 05, 2026 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
Update MultiVendorX to 5.0.11 or later. Review vendor accounts and REST requests for access to unrelated store identifiers, and assess exposed commission or financial records according to the site's data-handling obligations.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The MultiVendorX WordPress plugin before 5.0.11 does not verify that the requested store belongs to the current user in one of its REST API endpoints, allowing any vendor-level user to read other vendors' commission and financial data.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N