CVE-2026-19357

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-09. a secondary CVSS source baseline 5.3; sources differ by 0.0.

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

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

A security flaw has been discovered in MingSoft MCMS up to 3.0.6. Affected is an unknown function of the file /mdiy/form/get of the component ms-mdiy. The manipulation results in information disclosure. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 9, 2026

Last Modified

August 12, 2026

References (5)

Vendor Advisories for CVE-2026-19357(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 45× 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 01:17 UTCEG score recompute
  2. 2026-08-21 01:17 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 03:29 UTCEG score recompute
  5. 2026-08-20 03:29 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 05:41 UTCEG score recompute
  8. 2026-08-19 05:41 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 07:53 UTCEG score recompute
  11. 2026-08-18 07:53 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 10:03 UTCEG score recompute
  14. 2026-08-17 10:03 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 12:15 UTCEG score recompute
  17. 2026-08-16 12:15 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 14:28 UTCEG score recompute
  20. 2026-08-15 14:28 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 16:39 UTCEG score recompute
  23. 2026-08-14 16:39 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 18:51 UTCGHSA enrichment
Show 20 more
  1. 2026-08-12 21:03 UTCEG score recompute
  2. 2026-08-12 21:03 UTCGHSA enrichment
  3. 2026-08-12 13:50 UTCEPSS rescore
  4. 2026-08-12 12:05 UTCGHSA enrichment
  5. 2026-08-11 14:17 UTCEG score recompute
  6. 2026-08-11 14:17 UTCGHSA enrichment
  7. 2026-08-11 13:42 UTCEPSS rescore
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-10 16:29 UTCEG score recompute
  10. 2026-08-10 16:29 UTCGHSA enrichment
  11. 2026-08-10 16:29 UTCNVD updateCVSS v4 → 5.5
  12. 2026-08-10 16:10 UTCEG score recompute
  13. 2026-08-10 16:10 UTCGHSA enrichment
  14. 2026-08-10 16:09 UTCMITRE cvelistV5CVSS v4 → 6.9
  15. 2026-08-10 13:08 UTCEG score recompute
  16. 2026-08-10 13:07 UTCGHSA enrichment
  17. 2026-08-09 15:20 UTCEG score recompute
  18. 2026-08-09 15:19 UTCNVD updateCVSS v4 → 5.5
  19. 2026-08-09 14:56 UTCEG score recompute
  20. 2026-08-09 14:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19357?
CVE-2026-19357 is a medium vulnerability published on August 9, 2026. A security flaw has been discovered in MingSoft MCMS up to 3.0.6. Affected is an unknown function of the file /mdiy/form/get of the component ms-mdiy. The manipulation results in information disclosure. It is possible to launch the attack remotely. The exploit has been released to the public and…
When was CVE-2026-19357 disclosed?
CVE-2026-19357 was first published in the National Vulnerability Database on August 9, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19357 actively exploited?
CVE-2026-19357 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 78.7% of all scored CVEs.
What is the CVSS score of CVE-2026-19357?
CVE-2026-19357 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-19357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19357, 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-19357

Explore →

Is Your Infrastructure Affected by CVE-2026-19357?

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

Start Free Scan →Browse All CVEs