Quick answers
- Is CVE-2026-88416 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88416 being exploited in the wild.
- How severe is CVE-2026-88416?
- Informational severity, published 22 September 2026.
- Which products and versions are affected?
- Mingsoft Mcms 6.1.1, 6.2.0, 6.2.1.
- Is there a fix for CVE-2026-88416?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-88416 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-88416?
- Check whether you run Mingsoft Mcms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the custom model/form import endpoint (/ms/mdiy/form/importJson.do) which passes attacker-controlled SQL from the modelJson.sql field directly to JdbcTemplate.execute() after incomplete validation. Although the code attempts to restrict the first SQL statement to CREATE/ALTER TABLE operations, a keyword-based filter can be bypassed using CREATE TABLE AS SELECT statements combined with specific SQL constructs. The flaw requires authentication and appropriate permissions (mdiy:form:importJson), but allows extraction of arbitrary database schema information and data exfiltration via subsequent queries to the form data endpoint.
Affected products
- MingSoft MCMS 6.1.1, 6.2.0, 6.2.1
Timeline
- 2026-08-27: disclosed
- 2026-09-22: advisory