# CVE-2026-93341: MarketKing < 2.1.72 Missing Authorization via marketking_send_refund AJAX


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-j68h-v872-356w

## What is CVE-2026-93341?

CVE-2026-93341 is a medium-severity vulnerability in WebWizards MarketKing, published on 22 Sep 2026. 

### Official description

MarketKing plugin for WordPress before 2.1.72 contains a missing authorization vulnerability in the marketking_send_refund AJAX action that allows authenticated attackers with subscriber-level access or higher to create refund requests against any order by supplying an arbitrary order ID. Attackers can submit crafted AJAX requests targeting any order ID to create fraudulent refund requests against orders they did not place, enabling marketplace disruption and unauthorized interference with other users' orders.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-93341 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93341 is a medium-severity vulnerability in WebWizards MarketKing, published on 22 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-93341 in the wild and no public exploit code.

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

## Sources

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

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