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

CVE-2026-111685: IceCMS Unauthenticated SQL Injection

CVE-2026-111685 is an unauthenticated SQL injection vulnerability in IceCMS through version 4.1.5 that allows remote attackers to extract database contents. This post explains its technical details, affected versions, impact, and mitigation steps.

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-111685 Overview

CVE-2026-111685 is an unauthenticated SQL injection vulnerability in IceCMS through version 4.1.5. The flaw resides in the /WebResource/findresourcebynum endpoint, which accepts a user-controlled num path parameter. The application passes this value into a MyBatis-Plus QueryWrapper.last() call that concatenates data directly after the SQL LIMIT clause. Remote attackers can append arbitrary SQL using union-based or blind techniques to read database contents without authentication. The vulnerability is tracked under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).

Critical Impact

Unauthenticated remote attackers can extract arbitrary database contents, including credentials and session data, by sending a single crafted HTTP request to a public endpoint.

Affected Products

  • IceCMS versions through 4.1.5
  • WebResourceController component (findresourcebynum route)
  • Deployments exposing the IceCMS frontend /WebResource/ API

Discovery Timeline

  • 2026-10-16 - CVE-2026-111685 published to the National Vulnerability Database
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-111685

Vulnerability Analysis

IceCMS is a Java-based content management system that uses MyBatis-Plus for database access. The vulnerable handler in WebResourceController.java accepts a num path parameter and forwards it unchanged into a QueryWrapper.last() invocation. QueryWrapper.last() appends its argument verbatim to the end of the generated SQL statement, bypassing parameter binding entirely.

Because the attacker-controlled value is concatenated after the LIMIT clause, standard prepared-statement protection does not apply. An unauthenticated attacker can terminate the intended LIMIT fragment and append a UNION SELECT payload or a boolean-based blind payload to extract data from any table the application's database user can read. See the HackMD SQLi Analysis and the VulnCheck SQL Injection Advisory for the full request flow.

Root Cause

The root cause is unsafe use of the MyBatis-Plus QueryWrapper.last() API with untrusted input. last() is designed for appending static SQL fragments and performs no sanitization or binding. Routing a path parameter directly into this method converts a routine pagination feature into a string-concatenation SQL injection sink. The referenced WebResourceController source shows the concatenation pattern.

Attack Vector

Exploitation requires only network access to the IceCMS frontend. An attacker issues an HTTP GET request to /WebResource/findresourcebynum/{num} where the num segment contains SQL metacharacters. The injected payload executes within the database context of the IceCMS application user. No authentication, user interaction, or prior foothold is required. Both union-based extraction and blind time-based techniques are viable depending on database engine behavior.

// No verified public exploit code is available at the time of writing.
// Refer to the HackMD analysis and VulnCheck advisory linked above
// for a step-by-step description of the injection point in
// WebResourceController.findresourcebynum().

Detection Methods for CVE-2026-111685

Indicators of Compromise

  • HTTP requests to /WebResource/findresourcebynum/ where the trailing path segment contains SQL keywords such as UNION, SELECT, SLEEP, BENCHMARK, or comment sequences (--, /*).
  • Web server access logs showing abnormally long num path values or URL-encoded single quotes, parentheses, and whitespace.
  • Application or database error log entries referencing malformed SQL near the LIMIT clause originating from WebResourceController.
  • Outbound DNS or HTTP callbacks from the IceCMS host to unknown destinations following requests to the affected endpoint.

Detection Strategies

  • Deploy Web Application Firewall rules that inspect the num path segment for SQL metacharacters and reject non-numeric input.
  • Enable database query auditing to flag statements containing UNION SELECT or stacked queries originating from the IceCMS service account.
  • Correlate repeated 500-status responses from /WebResource/findresourcebynum/ with the originating client IP to surface blind-injection probing.

Monitoring Recommendations

  • Forward IceCMS access logs, application logs, and database audit logs to a centralized analytics platform for retention and correlation.
  • Alert on time-based anomalies where responses from /WebResource/findresourcebynum/ exceed baseline latency, which indicates blind time-based payloads.
  • Baseline normal num parameter values and alert on any request containing non-digit characters.

How to Mitigate CVE-2026-111685

Immediate Actions Required

  • Restrict public access to the /WebResource/findresourcebynum/ endpoint using network ACLs or a reverse proxy until a patched build is deployed.
  • Enforce strict server-side input validation that accepts only integer values for the num path parameter.
  • Rotate database credentials used by the IceCMS application and review audit logs for unauthorized reads.

Patch Information

No vendor-supplied fixed version was listed in the NVD entry at the time of publication. Monitor the upstream IceCMS GitHub repository and the VulnCheck SQL Injection Advisory for an official patch. Code owners should replace the QueryWrapper.last() concatenation with parameterized pagination that binds the limit and offset values rather than appending user input to the SQL string.

Workarounds

  • Place a WAF rule in blocking mode in front of IceCMS that rejects any /WebResource/findresourcebynum/ request whose final path segment is not a positive integer.
  • Add a reverse-proxy regex guard (for example in Nginx) that returns HTTP 400 when the num segment contains characters outside [0-9].
  • Restrict the IceCMS database account to least-privilege read access on only the tables required by the application to limit data exposure during an attempted exploit.
bash
# Nginx reverse-proxy guard for the vulnerable path
location ~ ^/WebResource/findresourcebynum/(.+)$ {
    if ($1 !~ ^[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.