How severe is GHSA-54wc-49qj-5ghj?

GHSA-54wc-49qj-5ghj has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-54wc-49qj-5ghj?

GHSA-54wc-49qj-5ghj affects the following packages: net.mingsoft:ms-mcms (Maven). Ecosystems affected: Maven.

How do I fix GHSA-54wc-49qj-5ghj?

Update net.mingsoft:ms-mcms to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-54wc-49qj-5ghj is resolved across your whole dependency graph.

How do I detect GHSA-54wc-49qj-5ghj in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.mingsoft:ms-mcms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-54wc-49qj-5ghj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-54wc-49qj-5ghj?

O3 pinpoints whether GHSA-54wc-49qj-5ghj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-54wc-49qj-5ghj actively exploited in the wild?

No public exploit code has been indexed for GHSA-54wc-49qj-5ghj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-54wc-49qj-5ghj?

GHSA-54wc-49qj-5ghj is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-54wc-49qj-5ghj published, and has it been updated?

GHSA-54wc-49qj-5ghj was published on October 17, 2025 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-54wc-49qj-5ghj

CRITICALFix: ming-soft/MCMS@35ccbf1

GHSA-54wc-49qj-5ghj is a critical-severity (CVSS 9.8) SQL Injection vulnerability in net.mingsoft:ms-mcms. O3 Security confirms whether GHSA-54wc-49qj-5ghj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MCMS vulnerable SQL injection via the content_title parameter

Also known asCVE-2025-56316

Published

Oct 17, 2025

Updated

Oct 21, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 21, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕net.mingsoft:ms-mcms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.mingsoft:ms-mcms`	≥ 5.5.0&&< 6.0.2	6.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.mingsoft:ms-mcms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update net.mingsoft:ms-mcms to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-54wc-49qj-5ghj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-54wc-49qj-5ghj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-54wc-49qj-5ghj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-54wc-49qj-5ghj in your dependencies?

O3 detects GHSA-54wc-49qj-5ghj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works