CVE
MultiVendorX broken access control in stores REST route
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.22
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. MultiVendorX plugin for WordPress before 5.0.22 Store_owner role has the edit_stores capability and per-store ownership checks are missing
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.21% · 11th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The MultiVendorX – WooCommerce Multivendor Marketplace plugin for WordPress has a broken access control flaw in its stores REST route that lets a logged-in vendor reach administrative flag handlers. Remotely, with a low-privilege account, an attacker can read other stores' contact emails, pending withdrawal amounts, onboarding and registration data, deactivation reasons, and visitor analytics.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
MultiVendorX plugin for WordPress before 5.0.22 contains a broken access control vulnerability in the /wp-json/multivendorx/v1/stores REST route that allows authenticated vendors to access administrative flag handlers due to the store_owner role possessing the edit_stores capability and missing per-store ownership checks. Attackers can exploit the insecure direct object reference in the visitorMap handler and other flag handlers to retrieve other stores' contact emails, pending withdrawal amounts, onboarding and registration data, deactivation reasons, and visitor analytics, resulting in a cross-tenant confidentiality breach.
Who should check
Marketplaces running the MultiVendorX WooCommerce multivendor plugin before 5.0.22 that allow vendor (store_owner) accounts.
Read the source excerpt
“MultiVendorX plugin for WordPress before 5.0.22 contains a broken access control vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
MultiVendorX plugin for WordPress before 5.0.22 Store_owner role has the edit_stores capability and per-store ownership checks are missingUpgrade to a fixed version: 5.0.22.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127211 (MultiVendorX WordPress Plugin < 5.0.22 Broken Access Control via stores REST Route), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127211 (entry last updated 2026-11-12):
Affected:
- MultiVendorX MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions: fixed in 5.0.22
Fixed versions: 5.0.22.
Conditions (all must be true for the bug to be hit):
- MultiVendorX plugin for WordPress before 5.0.22 (source: https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route)
- Store_owner role has the edit_stores capability and per-store ownership checks are missing (source: https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-127211 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127211 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://wordpress.org/plugins/dc-woocommerce-multi-vendor/#developers
- https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127211
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127211"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- MultiVendorX MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
fixed in 5.0.22
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127211
Is CVE-2026-127211 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A logged-in store vendor can use the plugin's stores REST route to read other stores' data, including contact emails, pending withdrawal amounts, onboarding and registration data, deactivation reasons, and visitor analytics. The store_owner role has the edit_stores capability, and per-store ownership checks are missing.Source: vulncheck.com
Which versions are affected by CVE-2026-127211?
MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions: before 5.0.22.Source: cve.now feed data
Am I affected, and how do I check?
The MultiVendorX plugin for WordPress, all versions before 5.0.22, is affected. The bug needs an authenticated vendor account with the store_owner role, so check the installed plugin version in the WordPress Plugins screen or the plugin's header.Source: vulncheck.com
How do I fix CVE-2026-127211?
Update the MultiVendorX plugin to version 5.0.22 or later. The facts name no other patch ids or workaround.Source: vulncheck.com