CVE-2024-46612VulnerabilityPublished 24 Sep 2024

CVE-2024-46612: iceCMS · n/a

Affects iceCMSSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubthecosy/iceCMS`pkg:github/thecosy/iceCMS`Other threats	Affected <=3.4.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, organizations should take immediate steps to mitigate the risk. These include: 1) Restrict network access to IceCMS instances by implementing IP whitelisting or VPN-only access to reduce exposure. 2) Monitor authentication logs for suspicious JWT usage or unexpected token issuance patterns. 3) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block forged JWT tokens or anomalous requests. 4) If feasible, disable JWT-based authentication temporarily and switch to alternative authentication methods. 5) Conduct a thorough audit of all accounts and tokens issued recently to identify potential compromises. 6) Plan for rapid deployment of patches or upgrades once available from IceCMS maintainers. 7) Educate administrators and developers about the risks of hardcoded cryptographic keys and enforce secure key management practices in future development. These targeted actions go beyond generic advice and directly address the exploitation vector and operational risk.

Description

IceCMS v3.4.7 and before was discovered to contain a hardcoded JWT key, allowing an attacker to forge JWT authentication information.

Impact

The impact of CVE-2024-46612 is severe for organizations using IceCMS, as attackers can fully bypass authentication mechanisms and gain unauthorized administrative access. This can lead to data breaches, unauthorized data modification or deletion, service disruption, and potential lateral movement within the network. Confidential information stored or managed by IceCMS can be exposed, undermining privacy and compliance requirements. The integrity of website content and user data can be compromised, damaging organizational reputation and trust. Availability may also be affected if attackers disrupt CMS operations or deploy malicious payloads. Given the ease of exploitation and the critical nature of the vulnerability, organizations worldwide face significant risk, especially those relying on IceCMS for content management in sensitive or high-profile environments.

Summary

CVE-2024-46612 identifies a critical security vulnerability in IceCMS versions 3.4.7 and earlier, where a hardcoded JWT signing key is embedded within the application. JWTs are widely used for stateless authentication, relying on cryptographic signatures to verify token authenticity. The presence of a hardcoded key means that an attacker who discovers this key can generate valid JWTs arbitrarily, effectively impersonating any user or administrative account without needing legitimate credentials. This vulnerability falls under CWE-321 (Use of Hard-coded Cryptographic Key), which is a severe security anti-pattern. The CVSS v3.1 score of 9.8 (Critical) reflects the vulnerability's ease of exploitation (network attack vector, no privileges or user interaction required) and its impact on confidentiality, integrity, and availability. Attackers can remotely bypass authentication, gain unauthorized access, manipulate data, and potentially disrupt services. Although no public exploits have been reported yet, the vulnerability's nature makes it a prime target for attackers once details become widely known. The lack of available patches at the time of disclosure increases the urgency for organizations to apply compensating controls or upgrade once fixes are released.

CWE-321Use of Hard-coded Cryptographic Key (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a hard-coded, unchangeable cryptographic key.
Architecture and Design
Prevention schemes mirror that of hard-coded password storage.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 07:28 UTC

WeaknessesCWE-321

Technical details

References

Community reviews

Related threats