# CVE-2026-16030: MStore API < 4.21.0 - Unauthenticated Account Takeover via Firebase Phone Authentication

> Unauthenticated attackers can forge tokens to take over user accounts, including administrators, in the MStore API WordPress plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-w2g6-85hw-mgcv

## What is CVE-2026-16030?

CVE-2026-16030 is a high-severity authentication bypass 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 correctly verify the cryptographic signature of the token used to authenticate its phone-based login, allowing unauthenticated attackers who know a registered user's phone number to forge a token and take over that user's account, including administrator accounts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-16030 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16030 is a high-severity authentication bypass 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: There is no known exploitation of CVE-2026-16030 in the wild and no public exploit code.

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

## Sources

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

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