# CVE-2026-16041: MStore API < 4.21.0 - Unauthenticated Product Review Creation

> Unauthenticated attackers can create fake product reviews on WooCommerce stores configured to restrict reviews to verified owners.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-9px3-jf5v-3473

## What is CVE-2026-16041?

CVE-2026-16041 is a high-severity missing authorization vulnerability in Unknown MStore API, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MStore API  WordPress plugin before 4.21.0 does not perform authorization or purchase-ownership checks on its REST product-review creation route, allowing an unauthenticated attacker to create WooCommerce product reviews with an attacker-chosen reviewer name, email and star rating on stores configured to accept reviews only from verified owners.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-16041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16041 is a high-severity missing authorization vulnerability in Unknown MStore API, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16041 exists.

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

## Sources

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

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