Skip to main content
VulnerabilityPublished Updated

CVE-2025-56316: MCMS · A SQL Injection

Affects MCMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubming-soft/MCMSpkg:github/ming-soft/MCMSOther threatsAffected
  • =5.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations using MCMS 5.5.0 should immediately audit their systems for exposure of the /cms/content/list endpoint and the usage of the content_title parameter. Until an official patch is released, implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting this parameter. Employ strict input validation and sanitization at the application layer, particularly for FreeMarker template inputs. Restrict database user privileges to the minimum necessary to limit the impact of potential injection attacks. Monitor logs for unusual SQL queries or errors indicative of injection attempts. Conduct penetration testing focused on this endpoint to verify the effectiveness of mitigations. Additionally, segment and isolate critical systems to prevent lateral movement if compromise occurs. Prepare incident response plans specific to SQL injection exploitation scenarios. Once patches become available, prioritize their deployment and verify their effectiveness through testing.

Description

A SQL injection vulnerability in the content_title parameter of the /cms/content/list endpoint in MCMS 5.5.0 allows remote attackers to execute arbitrary SQL queries via unsanitized input in the FreeMarker template rendering.

References

Community reviews

Loading reviews…