CVE-2026-16039

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 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 restrict its vendor-orders endpoint to the caller's own orders, allowing any authenticated user, including Subscribers, to read every WooCommerce order in the store together with each customer's personal information.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
45(Track)
EG Risk 45/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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
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 – Subscriber+ Order and Customer PII Disclosure via IDOR | CVE 2026-16039 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/85c6ff37-4761-420c-970f-05b2c50d3b28/

Vendor Advisories for CVE-2026-16039(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 19× in last 7d / 44× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 11:27 UTCEG score recompute
  3. 2026-08-20 11:27 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 10:03 UTCEG score recompute
  6. 2026-08-19 10:03 UTCGHSA enrichment
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 08:34 UTCEG score recompute
  9. 2026-08-18 08:33 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 07:06 UTCEG score recompute
  12. 2026-08-17 07:06 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 05:42 UTCEG score recompute
  15. 2026-08-16 05:42 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 04:18 UTCEG score recompute
  18. 2026-08-15 04:18 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 02:53 UTCEG score recompute
  21. 2026-08-14 02:53 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 01:29 UTCEG score recompute
  24. 2026-08-13 01:29 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 19 more
  1. 2026-08-12 00:05 UTCEG score recompute
  2. 2026-08-12 00:04 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 22:40 UTCGHSA enrichment
  6. 2026-08-09 21:15 UTCEG score recompute
  7. 2026-08-09 21:15 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 19:51 UTCEG score recompute
  10. 2026-08-08 19:51 UTCGHSA enrichment
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 18:26 UTCEG score recompute
  13. 2026-08-07 18:26 UTCGHSA enrichment
  14. 2026-08-07 18:07 UTCEG score recompute▲ 6.50
  15. 2026-08-07 18:07 UTCGHSA enrichment
  16. 2026-08-07 18:07 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  17. 2026-08-07 06:20 UTCNVD update
  18. 2026-08-07 06:03 UTCEG score recompute
  19. 2026-08-07 06:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16039?
CVE-2026-16039 is a medium vulnerability published on August 7, 2026. The MStore API WordPress plugin before 4.21.0 does not restrict its vendor-orders endpoint to the caller's own orders, allowing any authenticated user, including Subscribers, to read every WooCommerce order in the store together with each customer's personal information.
When was CVE-2026-16039 disclosed?
CVE-2026-16039 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-16039 actively exploited?
CVE-2026-16039 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 89.7% of all scored CVEs.
What is the CVSS score of CVE-2026-16039?
CVE-2026-16039 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16039, 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-16039

Explore →

Is Your Infrastructure Affected by CVE-2026-16039?

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

Start Free Scan →Browse All CVEs