Auth bypass in Mstore API

CVE-2026-16030

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.

Vulnerability class: Broken Authentication

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.004 (32.5th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 32nd percentile — 32.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-16030: held from 0.004 to 0.004.

EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000

Affected products

  • Mstore API — versions 0

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-16030?
CVE-2026-16030 is a high-severity vulnerability in Mstore API, classified under Improper Authentication. CVSS score: 8.1/10. Published 2026-08-07.
How severe is CVE-2026-16030?
High severity. CVSS v3 base score is 8.1 out of 10.