MultiVendorX store-owner REST access permits competing-store takeover
MultiVendorX before 5.0.11 exposes REST operations that do not verify that the targeted store belongs to the authenticated Store Owner. A vendor can supply another store's identifier and view, modify, take over or permanently delete that store. This unscored record received deeper review because a low-privilege cross-tenant authorization bypass permits destructive changes and privilege over another vendor's assets. The CNA does not disclose the routes, HTTP methods or identifier parameter.
- Component
- MultiVendorX
- Plugin slug
multivendorx- Affected
- < 5.0.11
- Safe version
5.0.11- Published
- Aug 05, 2026
- Weakness
- CWE-862 — Missing Authorization
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. Audit vendor REST activity and ownership, status and configuration changes for every store if a vulnerable release was exposed, and restore deleted records from a known-good backup where necessary.
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 store targeted through its REST API belongs to the requesting vendor, allowing an authenticated vendor (Store Owner and above) to view, take over, permanently delete, or modify any other vendor's store on the marketplace.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H