CVE-2026-16030

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

MStore API < 4.21.0 – Unauthenticated Account Takeover via Firebase Phone Authentication | CVE 2026-16030 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/adf8ffe0-39a2-4d26-af11-1ac807800735/

Vendor Advisories for CVE-2026-16030(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:55 UTCEG score recompute
  2. 2026-08-21 02:55 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 14:34 UTCGHSA enrichment
  5. 2026-08-20 02:16 UTCEG score recompute
  6. 2026-08-20 02:16 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 13:56 UTCGHSA enrichment
  9. 2026-08-19 01:35 UTCEG score recompute
  10. 2026-08-19 01:35 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 13:16 UTCGHSA enrichment
  13. 2026-08-18 00:57 UTCEG score recompute
  14. 2026-08-18 00:57 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 12:23 UTCGHSA enrichment
  17. 2026-08-17 00:04 UTCEG score recompute
  18. 2026-08-17 00:04 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 11:45 UTCEG score recompute
  21. 2026-08-16 11:45 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 23:27 UTCGHSA enrichment
  24. 2026-08-15 11:08 UTCEG score recompute
  25. 2026-08-15 11:08 UTCGHSA enrichment
Show 35 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 22:49 UTCGHSA enrichment
  3. 2026-08-14 10:30 UTCGHSA enrichment
  4. 2026-08-13 22:11 UTCEG score recompute
  5. 2026-08-13 22:11 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 09:52 UTCGHSA enrichment
  8. 2026-08-12 21:34 UTCEG score recompute
  9. 2026-08-12 21:34 UTCGHSA enrichment
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-12 09:15 UTCGHSA enrichment
  12. 2026-08-11 20:56 UTCEG score recompute
  13. 2026-08-11 20:56 UTCGHSA enrichment
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 08:38 UTCEG score recompute
  16. 2026-08-11 08:38 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 20:19 UTCGHSA enrichment
  19. 2026-08-10 08:00 UTCGHSA enrichment
  20. 2026-08-09 19:41 UTCEG score recompute
  21. 2026-08-09 19:41 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 07:23 UTCGHSA enrichment
  24. 2026-08-08 19:04 UTCEG score recompute
  25. 2026-08-08 19:04 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 06:45 UTCEG score recompute
  28. 2026-08-08 06:45 UTCGHSA enrichment
  29. 2026-08-07 18:26 UTCGHSA enrichment
  30. 2026-08-07 17:47 UTCEG score recompute▲ 8.10
  31. 2026-08-07 17:47 UTCGHSA enrichment
  32. 2026-08-07 17:47 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  33. 2026-08-07 06:20 UTCNVD update
  34. 2026-08-07 06:03 UTCEG score recompute
  35. 2026-08-07 06:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16030?
CVE-2026-16030 is a high vulnerability published on August 7, 2026. 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…
When was CVE-2026-16030 disclosed?
CVE-2026-16030 was first published in the National Vulnerability Database on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16030 actively exploited?
CVE-2026-16030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.4% of all scored CVEs.
What is the CVSS score of CVE-2026-16030?
CVE-2026-16030 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16030

Explore →

Is Your Infrastructure Affected by CVE-2026-16030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs