# CVE-2026-16746: MultiVendorX < 5.0.11 - Store Owner+ Cross-Store Commission Data Disclosure via commissions REST Endpoint

> A vendor can read other vendors' commission and financial data due to missing ownership verification in the REST API.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-xm3p-gghg-f4v9

## What is CVE-2026-16746?

CVE-2026-16746 is a low-severity missing authorization vulnerability in Unknown MultiVendorX, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The MultiVendorX  WordPress plugin before 5.0.11 does not verify that the requested store belongs to the current user in one of its REST API endpoints, allowing any vendor-level user to read other vendors' commission and financial data.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


## How do I fix CVE-2026-16746?

No fix has been published for CVE-2026-16746 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16746 being exploited?

There is no known exploitation of CVE-2026-16746 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16746 and fix it if it is affected.

What it is: CVE-2026-16746 is a low-severity missing authorization vulnerability in Unknown MultiVendorX, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16746 in the wild and no public exploit code.

Affected product: Unknown MultiVendorX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16746/ (Markdown: https://insights.sbomify.com/CVE-2026-16746/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16746
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16746
- OSV: https://osv.dev/vulnerability/CVE-2026-16746

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16746/
Summaries are generated and may contain mistakes; the official description above is the record.