Skip to main content
Vulnerability Database/CVE-2026-111686

CVE-2026-111686: IceCMS Unauthenticated SQL Injection Flaw

CVE-2026-111686 is an unauthenticated SQL injection vulnerability in IceCMS that enables remote attackers to extract database contents through the num parameter. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111686 Overview

CVE-2026-111686 is an unauthenticated SQL injection vulnerability in IceCMS versions up to and including 4.1.5. The flaw resides in the /WebArticle/findarticlesbynum endpoint, which accepts a num path parameter and concatenates it into a MyBatis-Plus QueryWrapper after the SQL LIMIT clause. Remote attackers can append crafted SQL payloads to extract arbitrary database contents using union-based or blind injection techniques. The weakness is tracked under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).

Critical Impact

Unauthenticated remote attackers can read sensitive database contents, including user credentials and administrative data, with a single HTTP request.

Affected Products

  • IceCMS versions up to and including 4.1.5
  • IceCMS backend module IceCMS-ment (WebArticleController)
  • Deployments exposing the /WebArticle/findarticlesbynum/{num} endpoint

Discovery Timeline

  • 2026-10-16 - CVE-2026-111686 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111686

Vulnerability Analysis

IceCMS is an open-source content management system written in Java using Spring Boot and MyBatis-Plus. The WebArticleController exposes an endpoint that returns a list of articles limited to a caller-supplied count. Instead of binding the num path parameter as a prepared statement value, the controller interpolates it directly into a QueryWrapper.last("LIMIT " + num) style call. MyBatis-Plus passes the resulting string to the database verbatim, which lets an attacker break out of the LIMIT clause and append arbitrary SQL.

Because the vulnerable route requires no authentication and runs over the network, any attacker reachable to the HTTP service can issue the request. Successful exploitation yields confidential database contents including article data, user records, and password hashes stored by the CMS.

Root Cause

The root cause is unsafe string concatenation of untrusted input into a SQL fragment. MyBatis-Plus QueryWrapper methods such as last() do not parameterize their arguments. The controller trusts the num path variable to be numeric but performs no validation, type coercion, or allowlisting before appending it to the query. This matches the classic SQL Injection pattern described in CWE-89.

Attack Vector

Exploitation requires only HTTP access to the vulnerable endpoint. An attacker issues a GET request to /WebArticle/findarticlesbynum/{num} where {num} contains a payload that terminates the LIMIT clause and introduces a UNION SELECT statement or a time-based blind condition. The underlying JDBC driver executes the appended SQL within the application's database context. See the HackMD write-up and the VulnCheck advisory for payload details. The vulnerable source is visible in the project's WebArticleController.

No verified exploit code is published with this advisory. Refer to the external references for sanitized payload examples.

Detection Methods for CVE-2026-111686

Indicators of Compromise

  • HTTP requests to /WebArticle/findarticlesbynum/ with non-numeric characters, SQL keywords (UNION, SELECT, SLEEP, BENCHMARK), or URL-encoded whitespace in the trailing path segment.
  • Unusually large or slow responses from the findarticlesbynum endpoint, indicating union-based or time-based extraction.
  • Database audit log entries showing SELECT statements originating from the IceCMS service account that reference system tables such as information_schema.

Detection Strategies

  • Deploy a Web Application Firewall (WAF) rule that rejects requests to /WebArticle/findarticlesbynum/{num} when num is not a positive integer.
  • Enable database query logging and alert on IceCMS-originated queries that reference metadata tables or contain UNION.
  • Correlate web access logs with application error logs for repeated 500 responses from the vulnerable route, which often indicate payload tuning.

Monitoring Recommendations

  • Monitor outbound data volume from the IceCMS host for anomalies consistent with bulk database extraction.
  • Track authentication logs for new administrator sessions following suspicious requests to the vulnerable endpoint.
  • Review MyBatis SQL logs for executed statements where the LIMIT clause contains more than a single integer token.

How to Mitigate CVE-2026-111686

Immediate Actions Required

  • Restrict network access to the IceCMS management interface to trusted administrators until a patched build is deployed.
  • Add a WAF or reverse-proxy rule that enforces a strict numeric regex (^[0-9]+$) on the num path segment of /WebArticle/findarticlesbynum/.
  • Rotate database credentials and any secrets stored in the IceCMS schema if exploitation is suspected.

Patch Information

At publication time no fixed release is referenced in the NVD entry. Monitor the upstream IceCMS GitHub repository for a release later than 4.1.5 that parameterizes the num input or replaces the QueryWrapper.last() concatenation with a safe pagination API. Review the VulnCheck advisory for updated remediation guidance.

Workarounds

  • Patch the WebArticleController to cast num to an int before use, rejecting any non-integer input with a 400 response.
  • Replace the QueryWrapper.last("LIMIT " + num) pattern with the MyBatis-Plus Page object or a prepared parameter binding.
  • Run the IceCMS database account with least privilege, removing access to information_schema and other schemas outside the application's needs.
bash
# Example nginx reverse-proxy guard enforcing a numeric path segment
location ~ ^/WebArticle/findarticlesbynum/(?<num>[^/]+)$ {
    if ($num !~ ^[0-9]+$) {
        return 400;
    }
    proxy_pass http://icecms_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.