# CVE-2026-19355: MingSoft MCMS ms-mdiy list.do ModelDataImpl.queryDiyFormData sql injection

> Remote attackers can exploit SQL injection in MingSoft MCMS via the formFields parameter to read or modify database contents.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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-mgf9-vmjp-7q9v

## What is CVE-2026-19355?

CVE-2026-19355 is a medium-severity SQL injection 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 vulnerability was determined in MingSoft MCMS up to 3.0.6. This affects the function ModelDataImpl.queryDiyFormData of the file /mdiy/form/data/list.do of the component ms-mdiy. Executing a manipulation of the argument formFields can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-19355 being exploited?

There is no known exploitation of CVE-2026-19355 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19355 is a medium-severity SQL injection 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: There is no known exploitation of CVE-2026-19355 in the wild and no public exploit code.

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-19355/ (Markdown: https://insights.sbomify.com/CVE-2026-19355/index.md)
```

## Sources

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

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