# CVE-2023-3201: MStore API <= 3.9.6 - Cross-Site Request Forgery to Order Title Update

> Unauthenticated attackers can trick administrators into updating order titles via forged requests due to missing nonce validation in the MStore API plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jun 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fg8x-c2rv-v75q

## What is CVE-2023-3201?

CVE-2023-3201 is a medium-severity vulnerability in inspireui MStore API – Create Native Android & iOS Apps On The Cloud, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The MStore API plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing nonce validation on the mstore_update_new_order_title function. This makes it possible for unauthenticated attackers to update new order title via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-3201?

It affects 1 product.


Products: Inspireui Mstore Api.

## How do I fix CVE-2023-3201?

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

## Is CVE-2023-3201 being exploited?

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

## Other vulnerabilities in inspireui MStore API – Create Native Android & iOS Apps On The Cloud

- [CVE-2024-6328](https://insights.sbomify.com/CVE-2024-6328/): MStore API – Create Native Android & iOS Apps On The Cloud <= 4.14.7 - Authentication Bypass (critical 9.8)
- [CVE-2023-3277](https://insights.sbomify.com/CVE-2023-3277/): MStore API <= 4.10.7 - Unauthorized Account Access and Privilege Escalation (critical 9.8)
- [CVE-2023-3076](https://insights.sbomify.com/CVE-2023-3076/): MStore API < 3.9.9 - Unauthenticated Privilege Escalation (critical 9.8)
- [CVE-2023-3077](https://insights.sbomify.com/CVE-2023-3077/): MStore API < 3.9.8 - Unauthenticated Blind SQLi (critical 9.8)
- [CVE-2023-3197](https://insights.sbomify.com/CVE-2023-3197/): MStore API <= 4.0.1 - Unauthenticated SQL Injection (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3201 and fix it if it is affected.

What it is: CVE-2023-3201 is a medium-severity vulnerability in inspireui MStore API – Create Native Android & iOS Apps On The Cloud, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-3201 in the wild and no public exploit code.

Affected product: inspireui MStore API – Create Native Android & iOS Apps On The Cloud. 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-2023-3201/ (Markdown: https://insights.sbomify.com/CVE-2023-3201/index.md)
```

## Sources

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

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