Skip to main content

MultiVendorX CVE-2026-74925

| EUVDEUVD-2026-75964 HIGH
Improper Privilege Management (CWE-269)
2026-09-11 WPScan GHSA-w9pm-mr7j-6qjf
7.2
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain or register vendor account
  2. Delivery
    Authenticate to WordPress site
  3. Exploit
    Call unprotected role settings update endpoint
  4. Execution
    Inject admin capabilities into vendor role
  5. Persist
    Re-authenticate to gain full admin access
  6. Impact
    Execute arbitrary code or exfiltrate data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must hold a valid vendor-role account on the target WordPress site running MultiVendorX < 5.0.16. No additional configuration is required - any site with vendor accounts enabled is vulnerable by default. Exploitation is limited to sites where (1) MultiVendorX is installed and active, (2) at least one vendor account exists or vendor registration is open to attackers, and (3) the plugin version predates 5.0.16. Sites that have never enabled the vendor role or have no external vendor accounts are not exploitable in practice. Authentication as a vendor (PR:L effectively) is the only meaningful barrier.

Impact

The supplied CVSS vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score 7.2), but PR:H is inconsistent with the described attack: the vendor role is a low-privileged marketplace seller, not an administrator. PR:L would be technically more accurate, which would raise the score to approximately 8.8. This discrepancy means the CVSS score likely understates real-world risk on multi-vendor marketplace sites where many untrusted third-party sellers register as vendors. No KEV listing was identified, so active exploitation in the wild is not confirmed. However, a publicly available exploit from WPScan substantially lowers the barrier to exploitation. The impact is maximum - full site takeover including C:H/I:H/A:H - making this a high operational priority for any site running MultiVendorX with external vendor registrations. The AC:L rating is appropriate: no special race condition, token, or configuration variation is needed.

Exploit ScenarioDerived

An attacker registers as a vendor on a MultiVendorX-powered WooCommerce marketplace (or uses an existing vendor account) and directly calls the unprotected role/capability settings update endpoint, appending administrator-level capabilities to the vendor role definition. On next login - or immediately if session is retained - the attacker's vendor account possesses full WordPress admin rights, allowing plugin installation, arbitrary PHP code execution, data exfiltration, and complete site compromise. A public exploit walkthrough is available via WPScan.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 11, 2026

Privilege escalation in MultiVendorX WordPress plugin before 5.0.16 allows authenticated vendor-role users to grant administrator-level WordPress capabilities to the vendor role, enabling full site takeover. The plugin's role and capability settings update mechanism fails to enforce access boundaries, letting any vendor - a legitimately registered but low-privileged marketplace seller - rewrite role permissions without restriction. A publicly available exploit exists via WPScan, and the vendor has released a patch in version 5.0.16.

RemediationAI

Update MultiVendorX to version 5.0.16 or later via the WordPress admin dashboard (Plugins → Installed Plugins → Update) or wp-cli ('wp plugin update dc-woocommerce-multi-vendor'). If immediate patching is not feasible, restrict new vendor registrations by disabling open vendor self-registration in MultiVendorX settings (Vendors → Settings → Registration), and audit existing vendor accounts for unexpected capability grants using a capability audit plugin or direct wp_user_roles database inspection. Note that disabling registration does not protect against already-registered vendors exploiting the flaw. The WPScan advisory at https://wpscan.com/vulnerability/04d64797-751a-4cdd-a37d-70afbad5d784/ provides additional detail.

Affected VersionsENISA

MultiVendorX 5.0.0 <5.0.16

Affected Packages

euvd multivendorx fix: 5.0.16

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MultiVendorX is a WooCommerce extension that transforms a WordPress site into a multi-vendor marketplace by introducing a custom 'vendor' role with scoped capabilities. WordPress's role and capability system (WP_Role/WP_Roles) allows plugins to define and update granular permissions. CWE-269 (Improper Privilege Management) applies here: the plugin exposes a role/capability settings update function without verifying that the requesting user has sufficient authority (e.g., administrator capability) to modify those settings. Because the vendor role itself can invoke this update, it can add administrator-level capabilities (such as manage_options or install_plugins) to its own role definition, effectively self-escalating to site admin. Affected CPE is cpe:2.3:a:unknown:multivendorx:*:*:*:*:*:*:*:* covering versions up to 5.0.16 (exclusive).

Know when Multivendorx gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Vendor role is low-privileged (PR:L not PR:H); network-accessible with no complexity; full CIA impact from site takeover.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 11, 2026 - 11:22 NVD
7.2 (HIGH)
Patch available
Sep 11, 2026 - 08:16 EUVD
CVE Published
Sep 11, 2026 - 06:00 cve.org
HIGH 7.2
CVE Published
Sep 11, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The MultiVendorX WordPress plugin before 5.0.16 does not restrict who can update its role and capability settings, allowing users holding its vendor role to grant that role administrator-level capabilities and take over the site.

Technical POC Analysis

Evidence caveat: the only source supplied is the WPScan advisory page.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

MultiVendorX WordPress plugin versions before 5.0.16 contain a privilege escalation vulnerability with publicly available exploit code allowing authenticated vendor-marketplace sellers to escalate to full administrator access and site takeover. Organizations running affected plugin versions face immediate risk of data theft, site compromise, and operational disruption.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
popular WooCommerce multi-vendor marketplace plugin, niche but widely deployed
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

56
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2026-16605 HIGH POC
7.2 Aug 05

Broken object-level authorization in the MultiVendorX WordPress plugin before 5.0.11 allows any authenticated vendor (St

CVE-2026-74926 HIGH POC
7.1 Sep 16

Broken access control in the MultiVendorX WordPress plugin (versions 5.0.0 through 5.0.15) allows any authenticated user

CVE-2023-5348 MEDIUM POC
6.1 Dec 18

The Product Catalog Mode For WooCommerce WordPress plugin before 5.0.3 does not properly authorize settings updates or e

CVE-2024-8289 CRITICAL
9.8 Sep 04

The MultiVendorX - The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to privi

CVE-2026-74927 MEDIUM POC
5.3 Sep 02

Unauthenticated information disclosure in the MultiVendorX WordPress plugin (versions prior to 5.0.15) exposes sensitive

CVE-2024-25929 CRITICAL
9.1 Jun 09

Missing Authorization vulnerability in MultiVendorX Product Catalog Enquiry for WooCommerce by MultiVendorX.0.5. Rated c

CVE-2024-31304 HIGH
8.8 Jun 09

Missing Authorization vulnerability in MultiVendorX WC Marketplace.1.3. Rated high severity (CVSS 8.8), this vulnerabili

CVE-2026-66441 HIGH
7.5 Aug 13

Unauthenticated broken access control in the MultiVendorX WordPress plugin (versions 5.0.10 and earlier) exposes restric

CVE-2025-48261 HIGH
7.5 Jun 09

CVE-2025-48261 is an information disclosure vulnerability in MultiVendorX that allows unauthenticated remote attackers t

CVE-2026-108695 HIGH
7.1 Oct 11

Authenticated vendor (store_owner) accounts in the MultiVendorX WooCommerce plugin through 5.0.19 can silently overwrite

CVE-2026-16746 LOW POC
2.7 Aug 05

Insecure Direct Object Reference (IDOR) in the MultiVendorX WordPress plugin before 5.0.11 exposes confidential financia

CVE-2026-81792 MEDIUM
6.5 Sep 08

Unauthenticated privilege escalation in the Product Catalog Enquiry for WooCommerce by MultiVendorX WordPress plugin (ve

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy