Skip to content
Unauthenticated SQL Injection Vulnerability in IceCMS 4.1.5

Unauthenticated SQL Injection Vulnerability in IceCMS 4.1.5

First seen 17 Oct 2026, 16:47 UTC •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 17, 2026 at 18:20 UTC
  • •IceCMS 4.1.5 is vulnerable to unauthenticated SQL injection.
  • •Attackers can exploit the WebResource and WebArticle endpoints to read database content.
  • •No patches have been released to address this vulnerability as of now.

IceCMS version 4.1.5 has been found to contain an unauthenticated SQL injection vulnerability affecting the WebResource and WebArticle preview endpoints. The endpoints, /WebResource/findresourcebynum/{content}/{num} and /WebArticle/findarticlesbynum/{content}/{num}, allow attackers to manipulate SQL queries by injecting arbitrary values into the 'num' parameter. This vulnerability is classified as CWE-89, which pertains to improper neutralization of special elements used in SQL commands. The issue arises from the lack of authentication checks due to the absence of certain controller prefixes in the Apache Shiro JWT filter chain. As a result, an anonymous attacker can exploit this flaw to read data from the IceCMS database. No patches or fixes have been reported as of the publication date. The vulnerability is currently and poses a significant risk to users of the affected version.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-17
Vulnerability disclosed
IceCMS 4.1.5 vulnerability affecting SQL queries was publicly disclosed, highlighting unauthenticated access.
hackmd.io
2026-10-17
Advisory published
Vulncheck published an advisory detailing the SQL injection vulnerability in IceCMS 4.1.5.
www.vulncheck.com

More articles in this cluster (2)

Extracted Entities (3)

1 / 4

Common questions

Which versions of IceCMS are affected?
IceCMS version 4.1.5 is affected by this SQL injection vulnerability.
Is there a patch available?
As of now, no patches or fixes have been released for this vulnerability.
How can I mitigate this vulnerability?
Until a patch is available, restrict access to the affected endpoints and monitor for suspicious activity.