CVE-2026-108695

MultiVendorX through 5.0.19 Incorrect Authorization via Settings REST Endpoint

Published Oct 11, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
MultiVendorX WordPress plugin through 5.0.19 contains an incorrect authorization vulnerability that allows vendor accounts to modify marketplace-wide settings via the settings REST endpoint. Attackers with the store_owner role can send POST requests to /wp-json/multivendorx/v1/settings, gated only by edit_stores, to overwrite commission, payout, and onboarding settings.

Analysis

AI-generated

Technical impact

The vulnerability lies in the settings REST endpoint of the MultiVendorX WordPress plugin, where authorization is incorrectly enforced. The API checks only for the edit_stores capability, which vendor accounts with the store_owner role possess, allowing them to POST to /wp-json/multivendorx/v1/settings and overwrite critical commission, payout, and onboarding configurations. According to CWE‑863, this lack of proper authorization enables privilege escalation and can undermine the integrity of the marketplace's financial settings.

Affected Systems

All installations of the MultiVendorX plugin running version 5.0.19 or earlier on WordPress sites are affected. The plugin, published under the multivendorx namespace, can be found in the WordPress plugin repository and its source code on GitHub. Users employing these versions should verify their plugin version and consult the advisory linked in the references.

Risk and Exploitability

The CVSS score of 7.1 classifies this issue as a high severity vulnerability. While EPSS data is unavailable and the vulnerability is not listed in the CISA KEV catalog, the exploitation path is straightforward: an authenticated store_owner can craft a POST request to the exposed REST endpoint. Successful exploitation results in unauthorized changes to marketplace settings, which could lead to financial loss or operational disruption.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the MultiVendorX plugin to the highest available version that resolves the authorization check.
  • Patch or block the specific REST endpoint by enforcing stricter capability checks or by adding a custom filter that verifies admin-level privileges before allowing settings changes.
  • Audit current commission, payout, and onboarding configurations for any unauthorized modifications and reset them as necessary to the intended values.

Generated by OpenCVE AI on October 11, 2026 at 03:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions multivendorx
Vendors & Products Wordpress-extensions
Wordpress-extensions multivendorx
Type Values Removed Values Added
Description MultiVendorX WordPress plugin through 5.0.19 contains an incorrect authorization vulnerability that allows vendor accounts to modify marketplace-wide settings via the settings REST endpoint. Attackers with the store_owner role can send POST requests to /wp-json/multivendorx/v1/settings, gated only by edit_stores, to overwrite commission, payout, and onboarding settings.
Title MultiVendorX through 5.0.19 Incorrect Authorization via Settings REST Endpoint
First Time appeared Multivendorx
Multivendorx multivendorx
Weaknesses CWE-863
CPEs cpe:2.3:a:multivendorx:multivendorx:*:*:*:*:*:wordpress:*:*
Vendors & Products Multivendorx
Multivendorx multivendorx
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 14, 2026, 2:43 AM
Reserved
Oct 10, 2026, 11:08 PM
Status
Deferred
Published
Oct 11, 2026, 2:16 AM
Modified
Oct 16, 2026, 7:18 PM