# CVE-2023-2732: MStore API <= 3.9.2 - Authentication Bypass

> Unauthenticated attackers can bypass authentication and log in as any existing user, including administrators, via the add listing REST API.

- **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:** 25 May 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q639-qhhx-5j5j

## What is CVE-2023-2732?

CVE-2023-2732 is a critical authentication bypass vulnerability in inspireui MStore API – Create Native Android & iOS Apps On The Cloud, published on 25 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MStore API plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 3.9.2. This is due to insufficient verification on the user being supplied during the add listing REST API request through the plugin. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user id.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Inspireui Mstore Api.

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

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

## Is CVE-2023-2732 being exploited?

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

Public exploit code:

- MStore API <= 3.9.2 - Authentication Bypass (github_poc): https://github.com/RandomRobbieBF/CVE-2023-2732
- Perform With Massive Authentication Bypass (Wordpress Mstore-API) (github_poc): https://github.com/Ap0dexMe0/CVE-2023-2732
- Python 2.7 (github_poc): https://github.com/Jenderal92/WP-CVE-2023-2732
- MStore API <= 3.9.2 - Authentication Bypass (nuclei): http/cves/2023/CVE-2023-2732.yaml

## 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-2732 and fix it if it is affected.

What it is: CVE-2023-2732 is a critical authentication bypass vulnerability in inspireui MStore API – Create Native Android & iOS Apps On The Cloud, published on 25 May 2023. 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-2023-2732 exists.

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-2732/ (Markdown: https://insights.sbomify.com/CVE-2023-2732/index.md)
```

## Sources

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

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