CVE-2026-16605

MultiVendorX < 5.0.11 - Store Owner+ Cross-Vendor Store Takeover and Deletion via Missing Authorization

Published Aug 5, 2026 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The MultiVendorX WordPress plugin allows an authenticated vendor to access its REST API without verifying that the target store belongs to the requesting vendor. This missing authorization step lets the vendor view, take over, modify, or permanently delete any other vendor's store in the marketplace, giving that vendor unauthorized control over another store's data. The bug falls under improper access control, allowing a vendor to perform actions reserved for the store owner or administrators.

Affected Systems

WordPress installations that use the MultiVendorX plugin version prior to 5.0.11 are affected. Any user with vendor or higher role who is authenticated can exploit this issue.

Risk and Exploitability

Because the flaw requires only an authenticated vendor account and can be exploited through the plugin's publicly documented REST API, the risk of privilege escalation is high. The CVSS score is 7.2, and the EPSS score is <1%, indicating a low probability of exploitation in the wild. The vulnerability is not listed in CISA KEV, suggesting it has not yet been observed in the wild. Regardless, the impact on data integrity and availability is significant, and the attack can be performed remotely through normal API traffic by mounting a credentialed attack.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MultiVendorX to version 5.0.11 or newer, which includes the missing authorization check.
  • If upgrading immediately is not feasible, restrict the REST API endpoints to verified store owners only by implementing a middleware check that confirms the store ID matches the authenticated vendor's store namespace.
  • Apply general WordPress hardening practices, such as enforcing least privilege for vendor roles, regularly patching WordPress core and all plugins, and monitoring API usage for anomalous activity.

Generated by OpenCVE AI on August 5, 2026 at 22:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-862
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Multivendorx
Multivendorx multivendorx
Wordpress
Wordpress wordpress
Vendors & Products Multivendorx
Multivendorx multivendorx
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
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.
Title MultiVendorX < 5.0.11 - Store Owner+ Cross-Vendor Store Takeover and Deletion via Missing Authorization
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 5, 2026, 7:41 PM
Reserved
Jul 22, 2026, 2:25 PM
Status
Deferred
Published
Aug 5, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM