# CVE-2026-108695: MultiVendorX through 5.0.19 Incorrect Authorization via Settings REST Endpoint

> Store owners can modify marketplace-wide settings like commissions and payouts due to incorrect authorization checks in the REST API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-h37j-r28p-597w

## What is CVE-2026-108695?

CVE-2026-108695 is a high-severity missing authorization vulnerability in MultiVendorX, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MultiVendorX WordPress plugin through 5.0.19 contains an incorrect authorization vulnerability that allows vendor accounts to modify marketplace-wide settings via the settings REST endpoint. Attackers with the store_owner role can send POST requests to /wp-json/multivendorx/v1/settings, gated only by edit_stores, to overwrite commission, payout, and onboarding settings.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-108695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108695 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108695 is a high-severity missing authorization vulnerability in MultiVendorX, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108695 exists.

Affected product: 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-108695/ (Markdown: https://insights.sbomify.com/CVE-2026-108695/index.md)
```

## Sources

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

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