# CVE-2024-8289: Missing authorization in MultiVendorX – WooCommerce Multivendor Marketplace Solutions

> Unauthenticated attackers can escalate privileges, create vendor accounts, or take over existing vendor accounts due to missing authorization checks in the MultiVendorX plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j558-547g-jpj8

## What is CVE-2024-8289?

CVE-2024-8289 is a critical missing authorization vulnerability in wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions, published on 4 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to privilege escalation/de-escalation and account takeover due to an insufficient capability check on the update_item_permissions_check and create_item_permissions_check functions in all versions up to, and including, 4.2.0. This makes it possible for unauthenticated attackers to change the password of any user with the vendor role, create new users with the vendor role, and demote other users like administrators to the vendor role.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-8289?

It affects 1 product.


Products: Multivendorx Multivendorx.

## How do I fix CVE-2024-8289?

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

## Is CVE-2024-8289 being exploited?

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

Public exploit code:

- CVE-2024-8289 https://www.cve.org/CVERecord?id=CVE-2024-8289, Vendor  wcmp  Product  MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution (github_poc): https://github.com/pashayogi/CVE-2024-8289

## Other vulnerabilities in wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions

- [CVE-2025-0493](https://insights.sbomify.com/CVE-2025-0493/): Path traversal in MultiVendorX – WooCommerce Multivendor Marketplace Solutions (critical 9.8)
- [CVE-2025-48261](https://insights.sbomify.com/CVE-2025-48261/): WordPress MultiVendorX plugin <= 4.2.22 - Sensitive Data Exposure Vulnerability (high 7.5)
- [CVE-2024-31304](https://insights.sbomify.com/CVE-2024-31304/): WordPress MultiVendorX Marketplace <= 4.1.3 - Broken Access Control vulnerability (high 7.1)
- [CVE-2025-48263](https://insights.sbomify.com/CVE-2025-48263/): WordPress MultiVendorX plugin <= 4.2.22 - Cross Site Scripting (XSS) Vulnerability (medium 6.5)
- [CVE-2024-5259](https://insights.sbomify.com/CVE-2024-5259/): Cross-site scripting in MultiVendorX – WooCommerce Multivendor Marketplace Solutions (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8289 and fix it if it is affected.

What it is: CVE-2024-8289 is a critical missing authorization vulnerability in wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions, published on 4 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8289 in the wild and no public exploit code.

Affected product: wcmp MultiVendorX – WooCommerce Multivendor Marketplace Solutions. 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-2024-8289/ (Markdown: https://insights.sbomify.com/CVE-2024-8289/index.md)
```

## Sources

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

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