CVE-2026-92404

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

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

The MgoSync WordPress plugin before 2.1.7 does not have authorization controls on one of its REST API endpoints, allowing unauthenticated users to retrieve the stored WooCommerce API credentials, including a read/write consumer key and secret, from a configured site.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 19, 2026

Last Modified

September 21, 2026

Advisory Details (1)

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

MgoSync 2.1.5 – 2.1.6 – Unauthenticated WooCommerce API Credential Disclosure | CVE 2026-92404 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/342e79ec-cfe6-43f3-8598-bf2b83aff2a1/

Vendor Advisories for CVE-2026-92404(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 31× in last 7d / 31× 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-09-25 10:56 UTCGHSA enrichment
  2. 2026-09-24 23:16 UTCEG score recompute
  3. 2026-09-24 23:16 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 11:38 UTCGHSA enrichment
  6. 2026-09-23 23:58 UTCEG score recompute
  7. 2026-09-23 23:58 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 12:19 UTCGHSA enrichment
  10. 2026-09-23 00:40 UTCEG score recompute
  11. 2026-09-23 00:40 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 13:01 UTCGHSA enrichment
  14. 2026-09-22 01:23 UTCEG score recompute
  15. 2026-09-22 01:23 UTCGHSA enrichment
  16. 2026-09-21 21:09 UTCEPSS rescore
  17. 2026-09-21 13:43 UTCGHSA enrichment
  18. 2026-09-21 13:02 UTCGHSA enrichment
  19. 2026-09-21 01:23 UTCEG score recompute
  20. 2026-09-21 01:23 UTCGHSA enrichment
  21. 2026-09-20 20:16 UTCEPSS rescore
  22. 2026-09-20 13:44 UTCGHSA enrichment
  23. 2026-09-20 02:06 UTCEG score recompute
  24. 2026-09-20 02:06 UTCGHSA enrichment
  25. 2026-09-19 14:27 UTCGHSA enrichment
Show 6 more
  1. 2026-09-19 13:25 UTCEG score recompute▲ 7.50
  2. 2026-09-19 13:25 UTCGHSA enrichment
  3. 2026-09-19 13:24 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  4. 2026-09-19 07:17 UTCNVD update
  5. 2026-09-19 06:26 UTCEG score recompute
  6. 2026-09-19 06:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92404?
CVE-2026-92404 is a high vulnerability published on September 19, 2026. The MgoSync WordPress plugin before 2.1.7 does not have authorization controls on one of its REST API endpoints, allowing unauthenticated users to retrieve the stored WooCommerce API credentials, including a read/write consumer key and secret, from a configured site.
When was CVE-2026-92404 disclosed?
CVE-2026-92404 was first published in the National Vulnerability Database on September 19, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92404 actively exploited?
CVE-2026-92404 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 65.0% of all scored CVEs.
What is the CVSS score of CVE-2026-92404?
CVE-2026-92404 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-92404?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92404, 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-92404

Explore →

Is Your Infrastructure Affected by CVE-2026-92404?

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

Book a Demo →Browse All CVEs