CVE-2026-108695

MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions <= 5.0.19 - Missing Authorization

2026-10-10 00:00
George Chen

Strategic Overview

Status
Unpatched
Affected Version
<= 5.0.19
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2026-108695
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

CVE-2026-108695 is a medium-severity Incorrect Authorization vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 5.0.19. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by George Chen.

Vulnerability Overview

The MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 5.0.19. This is due to a missing capability check on a function. This makes it possible for authenticated attackers, with vendor-level access and above, to overwrite commission, payout, and onboarding settings.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-863: Incorrect Authorization

Reaching this weakness in MultiVendorX <= 5.0.19 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. No fixed build of this plugin is recorded for MultiVendorX yet, so installs running <= 5.0.19 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C