LiveActive security incident?Get immediate response
CVE Record

CVE-2026-68000: The front-end interface /cms/category/list of MCMS <=6.2.0 is vulnerable to SQL injection.

The front-end interface /cms/category/list of MCMS <=6.2.0 is vulnerable to SQL injection. The size parameter is directly concatenated into the LIMIT clause of SQL through FreeMarker ${size} without being parameterized and bound. The built-in SqlInjectionUtil employs regular expression blacklist filtering, yet keywords like CREATE/TABLE/SET/PREPARE/EXECUTE are not included in the list, allowing for bypassing. Attackers can execute stacked SQL statements without logging in.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

MCMS deployments at version 6.2.0 or earlier may expose a public web endpoint that improperly inserts user input into database queries. The cited disclosure says an unauthenticated attacker could alter database operations, potentially exposing, changing, or destroying data and disrupting service.

Executive priority

Treat confirmed internet-facing MCMS 6.2.0-or-earlier deployments as an immediate remediation priority because the reported flaw could compromise confidentiality, integrity, and availability without authentication. Escalate exposed systems for containment while obtaining authoritative vendor guidance.

Technical view

The /cms/category/list endpoint reportedly inserts the size parameter directly into a SQL LIMIT clause through FreeMarker ${size}, without parameter binding. A regular-expression blacklist is described as incomplete, permitting bypasses and stacked SQL statements. The source assigns CVSS 3.1 score 9.8 under CWE-89.

Likely exposure

Internet-accessible MCMS installations running version 6.2.0 or earlier are the primary concern, especially where /cms/category/list is publicly reachable. However, the structured affected-product data says vendor and product are unavailable, so asset ownership and exact version scope require confirmation.

Exploitation context

The cited disclosure claims exploitation requires no authentication, user interaction, or elevated complexity. The provided record is not in KEV, and the source bundle provides no evidence of active exploitation in the wild. Public technical disclosure may nevertheless increase scanning interest.

Researcher notes

Evidence supports the described injection mechanism and critical CVSS assessment, but important gaps remain: no official vendor advisory or named fixed version is provided, structured vendor/product fields are unavailable, and active exploitation is unconfirmed. Validate product identity, reachability, logging, and any vendor fix independently.

Mitigation direction

  • Inventory MCMS deployments and prioritize systems running version 6.2.0 or earlier.
  • Check current MCMS vendor or maintainer guidance for an official patched release or mitigation.
  • Temporarily restrict external access to /cms/category/list where operationally feasible.
  • Apply compensating web filtering for anomalous size values, then monitor for bypasses.
  • Back up affected databases and verify restoration procedures before remediation.

Validation and detection

  • Confirm deployed MCMS versions using trusted package, build, or deployment records.
  • Determine whether /cms/category/list is reachable without authentication from untrusted networks.
  • Review request logs for unusual or SQL-like content in the size parameter.
  • Review database logs for unexpected statements associated with requests to the endpoint.
  • After remediation, conduct authorized non-destructive testing to confirm input is parameterized or safely rejected.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-68000 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-68000Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.