# CVE-2026-19357: MingSoft MCMS ms-mdiy get information disclosure

> Remote attackers can exploit the ms-mdiy component to disclose sensitive information via the /mdiy/form/get endpoint.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-mr8h-hjph-4g54

## What is CVE-2026-19357?

CVE-2026-19357 is a medium-severity vulnerability in MingSoft MCMS, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-19357?


## How do I fix CVE-2026-19357?

No fix has been published for CVE-2026-19357 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19357 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19357 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19357 and fix it if it is affected.

What it is: CVE-2026-19357 is a medium-severity vulnerability in MingSoft MCMS, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19357 exists.

Affected product: MingSoft MCMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19357/ (Markdown: https://insights.sbomify.com/CVE-2026-19357/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19357
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19357
- OSV: https://osv.dev/vulnerability/CVE-2026-19357

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19357/
Summaries are generated and may contain mistakes; the official description above is the record.