# CVE-2026-74925: MultiVendorX 5.0.0 - 5.0.15 - Store Owner+ Privilege Escalation to Administrator

> A vendor user can escalate privileges to administrator by modifying role settings, allowing full site takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-w9pm-mr7j-6qjf

## What is CVE-2026-74925?

CVE-2026-74925 is a high-severity vulnerability in Unknown MultiVendorX, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-74925 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74925 is a high-severity vulnerability in Unknown MultiVendorX, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74925 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-74925/ (Markdown: https://insights.sbomify.com/CVE-2026-74925/index.md)
```

## Sources

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

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