CVE-2026-57327

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-06-29. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

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

Subscriber Broken Access Control in MainWP <= 6.1.1 versions.

CVSS v3
6.3
EG Score
6.3(high)
EPSS
16.1%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-57327(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 24× in last 7d / 26× 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-07-07 00:23 UTCEG score recompute
  2. 2026-07-07 00:23 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:13 UTCEG score recompute
  8. 2026-07-06 02:13 UTCGHSA enrichment
  9. 2026-07-05 04:01 UTCEG score recompute
  10. 2026-07-05 04:01 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 05:50 UTCEG score recompute
  14. 2026-07-04 05:50 UTCGHSA enrichment
  15. 2026-07-03 07:34 UTCEG score recompute
  16. 2026-07-03 07:34 UTCGHSA enrichment
  17. 2026-07-02 09:24 UTCEG score recompute
  18. 2026-07-02 09:24 UTCGHSA enrichment
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 11:14 UTCEG score recompute
  21. 2026-07-01 11:14 UTCGHSA enrichment
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 13:03 UTCEG score recompute
  24. 2026-06-30 13:03 UTCGHSA enrichment
  25. 2026-06-29 14:53 UTCEG score recompute
Show 1 more
  1. 2026-06-29 14:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57327?
CVE-2026-57327 is a medium vulnerability published on June 29, 2026. Subscriber Broken Access Control in MainWP <= 6.1.1 versions.
When was CVE-2026-57327 disclosed?
CVE-2026-57327 was first published in the National Vulnerability Database on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57327 actively exploited?
CVE-2026-57327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57327?
CVE-2026-57327 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-57327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57327, 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-57327

Explore →

Is Your Infrastructure Affected by CVE-2026-57327?

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