---
title: "CVE-2026-108695: MultiVendorX WordPress Plugin - Broken Access Control"
description: "MultiVendorX WordPress plugin through 5.0.19 contains a broken access control vulnerability caused by insufficient authorization checks in the settings REST endpoint, letting attackers with store_owner role modify marketplace-wide settings via POST requests."
url: https://panop.io/threat-heartbeat/CVE-2026-108695/
---

# CVE-2026-108695 MultiVendorX WordPress Plugin - Broken Access Control

MultiVendorX WordPress plugin through 5.0.19 contains a broken access control vulnerability caused by insufficient authorization checks in the settings REST endpoint, letting attackers with store\_owner role modify marketplace-wide settings via POST requests.

CVSS base score 7.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.27% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-108695)

## Details

Type

Broken Access Control

Impact

Broken Access Control

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Published

11 October 2026

Updated

15 October 2026

Weakness

[CWE-863](https://cwe.mitre.org/data/definitions/863.html)

## Vendor fix

Update to the latest version of MultiVendorX WordPress plugin.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-108695](https://nvd.nist.gov/vuln/detail/CVE-2026-108695)
- [https://wordpress.org/plugins/dc-woocommerce-multi-vendor/](https://wordpress.org/plugins/dc-woocommerce-multi-vendor/)
- [https://www.vulncheck.com/advisories/multivendorx-through-5.0.19-incorrect-authorization-via-settings-rest-endpoint](https://www.vulncheck.com/advisories/multivendorx-through-5.0.19-incorrect-authorization-via-settings-rest-endpoint)
- [https://github.com/multivendorx/multivendorx](https://github.com/multivendorx/multivendorx)
- [https://github.com/multivendorx/multivendorx/blob/8a717799b02f698e4b2b61a282062a41fbe15183/plugins/multivendorx/classes/RestAPI/Controllers/Settings.php#L157-L172](https://github.com/multivendorx/multivendorx/blob/8a717799b02f698e4b2b61a282062a41fbe15183/plugins/multivendorx/classes/RestAPI/Controllers/Settings.php#L157-L172)
- [https://github.com/multivendorx/multivendorx/blob/8a717799b02f698e4b2b61a282062a41fbe15183/plugins/multivendorx/classes/RestAPI/Controllers/Settings.php#L77-L80](https://github.com/multivendorx/multivendorx/blob/8a717799b02f698e4b2b61a282062a41fbe15183/plugins/multivendorx/classes/RestAPI/Controllers/Settings.php#L77-L80)
- [https://github.com/multivendorx/multivendorx/issues/2375](https://github.com/multivendorx/multivendorx/issues/2375)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)