VulnerabilityPublished 6 May 2024Updated 2 Aug 2024

CVE-2024-33830: idccms · Cross-Site Request Forgery (CSRF)

Source CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.1High

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

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

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

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

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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 May 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate CVE-2024-33830, organizations should implement the following specific measures: 1) Introduce anti-CSRF tokens in all state-changing requests, especially for administrative endpoints like /admin/readDeal.php?mudi=clearWebCache, ensuring that requests are validated for authenticity. 2) Enforce strict origin and referer header checks to verify that requests originate from trusted sources within the application domain. 3) Limit access to administrative interfaces by IP whitelisting or VPN-only access to reduce exposure. 4) Educate administrators about the risks of interacting with untrusted links or websites while logged into the CMS. 5) Monitor web server and application logs for unusual or repeated requests to the vulnerable endpoint that could indicate attempted exploitation. 6) Implement Content Security Policy (CSP) headers to reduce the risk of malicious content injection that could facilitate CSRF attacks. 7) Regularly review and update the CMS to the latest versions once patches addressing this vulnerability become available. 8) Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block CSRF attack patterns targeting the affected endpoints. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable component and attack vector.

Description

idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/readDeal.php?mudi=clearWebCache.

Impact

The primary impact of CVE-2024-33830 lies in the potential unauthorized execution of administrative actions, specifically clearing the web cache, which can compromise the confidentiality and integrity of the affected systems. Clearing the cache unexpectedly can lead to exposure of sensitive data, disrupt normal content delivery, and potentially allow attackers to bypass security controls or cause inconsistent application states. While availability is not directly affected, the operational disruption and potential data exposure pose significant risks. For organizations worldwide using idccms 1.35, this vulnerability could facilitate further attacks by weakening security postures or enabling privilege escalation through indirect means. The lack of authentication requirements for the attacker and the ease of exploitation via user interaction increase the threat level, especially in environments where administrators frequently access the CMS from browsers. This vulnerability could be leveraged in targeted attacks against organizations relying on idccms for content management, particularly those with sensitive or regulated data. The absence of known exploits in the wild currently limits immediate widespread impact, but the high CVSS score suggests that exploitation could have severe consequences if weaponized.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/xyaly163/cms/blob/main/2.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:36 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats